Anyone Ran into this bug? Gotta Fix? KB915782

Mark Kucera <[email protected]>
Newsgroups gmane.comp.windows.devel.dotnet.web
Message-ID <[email protected]>
Has anyone here experienced either of the errors in KB915782?

http://support.microsoft.com/kb/915782/en-us

I've got a 2.0 ASP.NET site that uses the Web Application Project model
and all the files are compiled into a single assembly.  The error I am
getting is the 2nd one listed in the KB article "Could not load file or
assembly...".   The site where this is running also hosts several .asp
pages and files of other types including .pdf, .swf, .exe, .zip, & .xml
as well as tons of .jpg and .gif images.  The new ASP.NET project model
doesn't really suit this site too well, with its lack of project files
like we had in 1.x I only work on the .net side of this website and
can't trust that the .asp files on my system are the same as the server,
and I can't afford for all the project files to get deleted prior to new
site being coppied etc so that is part of the reason I've switched this
site over to the Web Application Project model.

Since this site has gone live using 2.0, it has randomly been afflicted
by this error mentioned in the link above.   Several web searches on
this error seemed to indicate that many people had applied the Hotfix to
no avail.  That describes my situation as well.  Less than a week after
the Hotfix was applied the same error occurred.  The errors seem to be
completely sporadic and generally *but not always, occur after hours.

I am curious if anyone else here has had to deal with this issue and if
so if they could offer any input on possible resolution.

Thanks so much!
MK

===================================
This list is hosted by DevelopMentor®  http://www.develop.com

View archives and manage your subscription(s) at http://discuss.develop.com
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.