Last post Jan 19, 2007 12:11 PM by tony_lombardo
Jan 18, 2007 05:15 PM|troyparsons|LINK
Create a (strongly) named class library.
Now put this assembly somewhere on your harddrive.
Create a web.config something like the following:
<add assembly="Some.Class.Library, Version=22.214.171.124, Culture=neutral, PublicKeyToken=c7baf623fbfe5760"/>
<assemblyIdentity name="Some.Class.Library" publicKeyToken="c7baf623fbfe5760" culture="neutral"/>
<codeBase version="126.96.36.199" href="file:////c:/development/buildproblems/externallibs/Some.Class.Library.dll"/>
This will work fine with with the aspnet_compiler, but will choke aspnet_merge/.wdprojs with the following error:
An error occurred when merging assemblies: Unresolved assembly reference not allowed: Some.Class.Library.
This occurs whether or not you build inside VS.Net or use MSBuild directly.
I really hope someone can help with this - it's a big problem for us. I work with a very large company (like deathstar big), supporting a large developer base. We resolve all shared assemblies from a central repository - the GAC can't scale in our environment
- and use linked configuration files to specify binding redirects. Additionally, this is a big thorn in the side of developers trying to use any build environment to build their ASP.Net applications. I'm not going to repeat all the reasons why standard ASP.Net
2.0 compilation model has some holes in it... but if anyone can offer any information about this problem or can fix it, that would be most appreciated!
Jan 19, 2007 12:11 PM|tony_lombardo|LINK