Configuration :: SerializationException Occurring Only In Release Build?
Mar 19, 2010
I am working on an ASP.NET web app using Visual Studio 2008 and a third-party library.
Things are fine in my development environment. Things are also good if the web app is deployed in Debug configuration. However, when it is deployed in Release mode, SerializationExceptions appear intermittently, breaking other functionality.
In the Windows event log, the following error can be seen:
"An unhandled exception occurred and the process was terminated.
Message: Unable to find assembly 'MyThirdPartyLibrary, Version=184.108.40.206, Culture=neutral, PublicKeyToken=3d67ed1f87d44c89'.
StackTrace: at System.Runtime.Serialization.Formatters.Binary.BinaryAssemblyInfo.GetAssembly()
at System.Runtime.Serialization.Formatters.Binary.ObjectReader.GetType(BinaryAssemblyInfo assemblyInfo, String name)
at System.Runtime.Serialization.Formatters.Binary.ObjectMap..ctor(String objectName, String memberNames, BinaryTypeEnum binaryTypeEnumA, Object typeInformationA, Int32 memberAssemIds, ObjectReader objectReader, Int32 objectId, BinaryAssemblyInfo assemblyInfo,
Using FUSLOGVW.exe (i.e., Assembly Binding Log Viewer), I can see the problem is that IIS attempts to find MyThirdPartyLibrary in directory C:windowssystem32inetsrv. It seemingly refuses to look in the bin folder of the web app, where the DLL is actually located.
I have few confusions about build. What is release build and debug build? What are the output files for these builds? I had seen debug and release folders in bin folder. So the respective output goes into the respective folder? elaborate release and debug build. I dont want the difference.
We have an ASP.Net MVC solution built in VS2008 and TFS2008. We use TFS Build and use Continuous Integration.We have a deployment pipeline that enables us to progress a build, eventually, to our live site...
Internal Dev (immediate deployment following a build) External Dev (used by internal testers to make sure it works on the production server) External Test (used by our client to test themselves) Live (self explanatory).
I have 2 questions relating to thisWhich ones of these should be built in Debug and which in Release?How should I write my TFSBuild.proj files to cope with this strategy?
this is used when loading certain assets (swf files) by being appended as a querystring parameter and ensures that when debugging a cached version isn't received but is manageable once released.
However, after what I believed should be compiling a relase build, the version is still being set as a Guid indicating I'm not achieving a release build yet. I've checked the web.config and the value of debug is changed to false so I'm assuming I'm missing some setting in the aspnet_compiler.exe arguments, but I cant find anything which indicates such in the documentation.
I have a VS2010 Web Application that uses the AjaxControlToolkit. I am able to build the Debug configuration. When I build the release configuration I get the following error message: Error 89 Could not load file or assembly 'file:///S:My CodeLibrariesACTMay 2010AjaxControlToolkit.dll' or one of its dependencies. Operation is not supported. (Exception from HRESULT: 0x80131515) S:My CodeEZFishingEZFishingEZFishingSGEN EZFishing
The location of the file is correct, and I just downloaded and unzipped there the Ajax CT. I have always built this app correctly before upgrading to VS2010 and ACT May 2010.
When I run my app locally I get no errors. No error from Global.asax, no redirection to an error page. Everythings works fine.
When I deploy my app to a test server, my app run there with no errors. No error from Global.asax, no redirection to an error page. Everythings works fine on the test server.
But when I deploy my app to production server, the app runs fine but I keep getting errors (emailed to me) from Global.asax. On production server we have these security apps that run and keep hitting all URLs of the app on the server. Just to make sure they are working fine. When these security app hit URL of my app, my application runs fine but it gives out this global.asax error. The funny thing is that error is empty. The error are emailed to me and the email is empty. Nothing there.
There are several other apps running on the same server. My app has its own app pool and is configured correctly.
I got a project when after opening in visual studio 2005 in build mode drop down, only debug mode is shown but release mode not shown.Project builds successfully in debug mode is there a way to enable release mode.
Visual Studio 2008 I have web application in production where Web project is using Business project (.dll). Now i have made some changes in Business and need to move, say business.dll, to production. I am changing the version number of new business dll. While deploying it is giving error (System.IO.FileLoadException: Could not load file or assembly... ) and web project is not able recognige business.dll becuase version has changed now. I do not want to release web project as there are no changes there.
I'm on Windows Server 2008 with IIS 7.5 I have set up two web applications on the web site; one for the debug-build and one for the release-build for our system. I have not been able to figure out how to setup the two web applications so that they do not share the same native module.
I have tried many different configuration but obviously there is something I do not understand.
These are the changes I have made to applicationHost.config:
Under the section <globalModules> the following to rows are added at the end:
<add name="RXDebug" image="g:workspaces ewreposdebuginRXWeb.dll" /> <add name="RXRelease" image="g:workspaces ewrepos eleaseinRXWeb.dll" /> The web.config for the debug-application looks like this: <?xml version="1.0" encoding="UTF-8"?> <configuration>............
I have a WCF service than in my development and production environments works without any trouble but in my test environment it will occasionally throw a CommunicationObjectFaultedException. This has been very difficult to track down but it seems to happen only after going a long time with out calling it.client is a web applictaion running on two load balanced servers, the WCF service is hosted in IIS and running on two load balanced servers.There is no difference in the WCF configuration between the three environments so I believe there must be something different in the way the servers are set up. What are some things I can ask my server admins to check? (I don't have proper access to these servers to check stuff myself).
I have a folder in my project that contains files I do not want to process (they are only for reference) when I build the web site. These files produce errors because they reference things I do not have in my site. How can I exclude a folder so that it is not processed during a build?
I've been doing this project at work on a little app that we use for building and deploying websites to different customers. It works quite well, and we actually only have to press two buttons to have our DataProviders and DataRecords generated from sql and having our dll's compiled and everything sent to the customers ftp as a zip file, ready to unpack and use.
Now the problem is that since I've upgraded to Windows 7 (was XP) our compiler (either csc.exe or the msbuild.exe) seems to be messing with the codepage of our generated files. Resulting in æøå and characters alike are being converted to what seems to be ANSI encoding (this doesn't happen when running on XP).
I've been searching the net to find a viable solution to our problem and the only thing I have come upon is that the .NET framework version 4 has a parameter for codepage. Since we are using webdeploy build files on the 2.0 framework (and don't have time to roll our projects on to the next version framework) I would like to know if anyone has a quick remedy to resolve our problems with codepage.
I would like to make the build information for the running web application but I dont know where I set or configure this nor do I know how to retrieve this information.
In a project you may set the build information in the file AssemblyInfo.cs under the projects Properties folder. Here is a snippet of the AssemblyInfo.cs file:
But there is no such file for an web application project, so I have to get this information from one of the compiled DLLs that is in the same assembly as my web application then? Or how is this done?
The reason I want this information is because my customer would like to have a webpage within the web application where he could see the current version. This is also nice to have when testing and debugging etc.
I am receiving an error: The parameter 'configFileBaseName' is invalid when trying to build a project on my macintosh thru a windows server 2003 VMwAre fusion virtual machine This solution runs fine on Visual Studio 2010 on my PC running Windows 7 I don't think the platform has anything to do with the error though - but cannot find anything on the web to help me troubleshoot the problem. Something tells me this has more to do with setting up my IIS site configuration - perhaps I missed something?