Ignoring Assembly Versions

[Mark Redman]

Hi All,

We have some reporting in our asp.net apps, we use Active reports but this
could apply to any reporting tool. These reports get compiled into the app
and generally we deploy the complete site for any updates/changes etc.

My plan is create a project(dll) within a site's solution specifically for
the reporting side of the app, this project will reference the reporting
tool's dll's. Functions that run a report will return the report as a byte[]
array so I can use this to either write to file or binary write to the
browser.

I want to be able to make report changes and only drop in the Reporting dll
(and reporting tool dll's if a new version is available) to make report
updates without having to deploy the rest of the site. If I drop in a new
repoting dll that is referenced by the project, I would get an error
indicating an incorrect assembly version reference.

Is it possible to ignore the version reference. Obviously changing functions
parameters etc would lead to other errors, but I am just talking about
report content changes/updates/bug fixes etc.

Hope this makes sense?

Mark Redman

 

[Erik Frey]

Is it possible to ignore the version reference. Obviously changing functions
parameters etc would lead to other errors, but I am just talking about
report content changes/updates/bug fixes etc.

Hope this makes sense?

Mark Redman

Mark,

Have you considered using a plugin architecture? .NET reflection makes this
very easy to implement:

http://www.codeproject.com/csharp/C__Plugin_Architecture.asp

Erik

 

[Mark Redman]

Hi Erik,

Thanks for the reply, I will have a look at that.

Mark