Windows Server

Narshe · Guest

I'm getting this error

The located assembly's manifest definition with name 'MyAssembly' does
not match the assembly reference.

when opening a webpart. The webpart hosts user controls, and both the
webpart and the user controls have built from a framework. The
webparts, user controls, and framework are all in seperate solutions.
All files are being built to the bin. All the assembly versions were at
1.0.0.0, but I just moved the framework dll's to 1.0.* so we could put
multiple versions of the framework up for each webpart, as to not break
existing webpart functionality.

Everything worked fine using 1.0.0.0, and using 1.0.* works fine when
deploying these to the GAC. Having 1.0.* on my local maching with
building to the bin isn't working, and gives me the error.

I have tried everything thing I can think of, but I can't get the
webpart with the user controls to display. Webparts that don't have the
user controls seem to display fine.

Here is some more tracing info.

=== Pre-bind state information ===
LOG: DisplayName = MyAssembly, Version=1.0.2139.29381, Culture=neutral,
PublicKeyToken=8d0859d70306b163
(Fully-specified)
LOG: Appbase = file:///C:/Inetpub/MySite
LOG: Initial PrivatePath = bin
Calling assembly : (Unknown).
===

Narshe · Guest

Also, if I change them all back to 1.0.0.0 I get the same thing.
Something is being cached somewhere. Doing an iisreset doesn't help,
nor does restarting the whole maching. Here is some more trace info.

LOG: Publisher policy file is not found.
LOG: No redirect found in host configuration file
(C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet.config).
LOG: Using machine configuration file from
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\config\machine.config.
LOG: Post-policy reference: MyAssembly, Version=1.0.2139.29381,
Culture=neutral, PublicKeyToken=8d0859d70306b163
LOG: Attempting download of new URL
file:///C:/WINDOWS/Microsoft.NET/Framework/v1.1.4322/Temporary ASP.NET
Files/root/4ae1c7fc/7b10a8b6/MyAssembly.DLL.
LOG: Attempting download of new URL
file:///C:/WINDOWS/Microsoft.NET/Framework/v1.1.4322/Temporary ASP.NET
Files/root/4ae1c7fc/7b10a8b6/MyAssembly/MyAssembly.DLL.
LOG: Attempting download of new URL
file:///C:/Inetpub/MySite/bin/MyAssembly.DLL.
WRN: Comparing the assembly name resulted in the mismatch: Revision
Number

Narshe · Guest

I found the reason. When changing the version number for a dll,
rebuilding says it's using the new version number, but if I open the
dll with ildasm and look at the manifest for the dll it's actually
using, it didn't pick up the new version. The only to get it to pick up
the new version is to close, reopen, and rebuild the solution.

The located assembly's manifest definition with name 'MyAsse

	Windows Server Forum Index -> Portal Server Development	All times are GMT
Page 1 of 1