Visual Studio :: System.TypeInitializationException When Executing A 4.0 Web Application In Debug Mode?
Feb 11, 2011
There are plenty other similar static methods defined within the class.
When does it fail: ONLY when the solution is compiled in 'DEBUG' mode. Everything works fine in 'RELEASE' mode.
What have I already tried:
1. Including a static constructor inside 'Utility' class - FAILED
2. Marking 'Utility' class with 'static' keyword: FAILED
3. Changing platform target from 'Any CPU' to 'x64': FAILED
As highlighted above, the issue is really not with VerifyPassword() method per se. Rather it is with the instantiation of 'Utility' type. That's why an exception is thrown from the constructor. Since 'VerifyPassword' is it is the first static method called, it appears in the stack. Just for the sake of proving that, I removed the call to VerifyPassword and returned 'true' instead. That way I was able to login to the application (no password verification), but failed at a later stage where I had called the Utility class on another method, namely Utility.ValidateSKUAdjustment(txtCurentMonthM1.Text).
First time i am going to work on (maintenance project) application that is already in production.The application was developed in ASP.net 3.5/C# 3.0(web forms) with jQuery,Ajax,Sql server 2005 and microsoft enterprise library 4.0.,WCF services. Questions (bear with me if my question is wrong)
1) Is it possible to use Visual Studio (2008 with SP1) to debug the remote application (i.e already in production)?.What are the tools do i need to use in order to keep track the things in case something went wrong?
2) Simply looking into Log file ,will solve the issues?
3) After having done with enhancements,is it possible to directly deploy the DLLs into production server.Won't it affect the running application?
what are the procedures i need to follow.Client is ready to provide any tools for my support.(What are the area do i need to aware to handle production system
I got a problem regarding CSS in my pages. I managed to apply styles to my page using css and everything looks fine in the Design view. I ran it on IE8 and everything is working fine. Now after I returned to Visual Studio, added some rules to my CSS, and noticing that everything is working fine in the Design view, I ran it again in IE8 and nothing has changed. The rules I added was ignored and it looks the same. I ran it on Firefox and Google Chrome and it's working fine.
But if I ran my project in IE8 through IIS7.5, everything is working fine so it means, the problem is within visual studio 2010.
I am using vs2008 sp1. I am building web site with aspx. I am also using an ajax control. My Site was working normally. I could run it from f5 and it would stop at a debug point. I added an additional aspx page. Then I got a strange error. When I pressed f5 a message box appeared saying that I had not made this version with the debug option. Then from reading an internect post I disabled only my code. That got rid of the message box error but now the debugger does not stop at any break point? Of course this happen when I need to go live with this project in a day.
I am developing a web site in Visual Studio 2008. I have a project for the web application and several class libraries as references. When I add the references I select the file under bin/debug in the class library folder. When changing the project to release mode the references still point to the .dll in the debug folder. Shouldn't this change automatically. How should I add the references so that debug and release are properly referenced?
We all know that we should only be publishing our ASP.NET Web Applications with release build type, so why do I not get a warning when I trigger the "Publish" command in Visual Studio 2008, for a project configured to build in debug mode? Sure, there might be cases where I need to publish a debug build to a development or test environment, but answering yes in a confirmation dialog would be acceptable in these cases. Is there an option that I have overlooked, forcing Visual Studio to warn me every time I try to publish a debug build? Yes, we could just ban using the "Publish" command and use a more solid build management tool, but this involves a change of process and right not be an option in this particular case.
I am using Visual Studio 2010 and ASP.NET 4.0 to build a WebForms project that uses the new routing features in System.Web.Routing. When I build my solution and run it from within VS.NET's debugging environment only routes with RouteUrl's that include a ".aspx" extension are being properly routed to the PhysicalFile. It appears requests made to other URLs are not being "detected" by the routing engine for processing. In the case below, "Scenario1" shows a 404 and "Scenario2" works properly.
I am developping an MVC3 RC2 application and just after hitting F5 on my asp web application, I am getting this error message program ' w3wp.exe: Managed (v4.0.30319)' has exited with code -2 (0xfffffffe).So I am totally unable to debug my application
The default ASP.NET web server that launches from within Visual Studio (Casini) is a little buggy on my development machine, so I like to publish to a local IIS instance on my dev machine and look at the web application there. However, I'm not automatically in "Debug Mode" when I launch the application this way.
I know that VS 2010 has an "Attach to Process" debug feature, but I'm not sure exactly how to use it. What do I need to do to be able to debug a local IIS ASP.NET web application from within Visual Studio? Specifically:
What settings do I need to change in the configuration of my web application?
What "Package/Publish Settings" do I need to change?
Is there anything I need to change in IIS?
Is there anything special I need to do in the "Attach to Process" screen?
Background Information: I'm running Visual Studio 2010 on Windows XP SP3 with IIS 5.1 and .NET 4.0.
I should add that I've tried attaching to aspnet_wp.exe, but when I go to a page that I know has a breakpoint in it, I get the following message when I hover over the "open circle" breakpoint:
The breakpoint will not currently be hit. No symbols have been loaded for this document.
I'm running ASP.NET on Visual Studio 2005, and I am not able to step through my break points when I run my application in "Debug" mode. I set the break points, run the application, and Visual Studio simply ignores them.I have gone through all of the configuration settings and project properties to see if their is something obvious that needs to be turned "on" - but I don't see anything.What would be the most logical settings or references to look at?
Debug-Start Debugging/Debug-StartWithoutDebugging OR Project ASP.Net Configuration launches Dreamweaver. It started lastnight, I had both Deamweaver and VWD 2008 express open at the same time - (I was looking at JQuery in the Microsoft and Dreamweaver enviroments simultaniously). After the first tie this happened, I closed down Dreamweaver (CS3) and it opened when I tried to run my VWD project. I reinstalled VWD 2008 express, IIS and disabled Dreamweaver (renamed the exe). Dreamweaver still came up.
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.
I'm opening some project off of the codeplex website. When I do, it lists two types of files: *.cs and *.debug.cs me what the *.designer.cs" are?Also, when I build the application, it creates a "dll" in the "debug" directory. How do I make a dll get built in the "release" directory?
I tried to install Visual Studio Prof 2010 trail version in my system, but i got an error saying 'Please remove/uninstall Visual Studio 2010 load test controller' to proceed installation. i uninstalled my previous VS2008 software from system and i could not find anything like 'Remove/Uninstall Visual Studio 2010 load test controller' software in my Add/Remove Programs.
I have deployed a web service on my development machine and i am connecting it through my asp.net application, both web service and asp.net application are on same machine but web service is hosted on IIS.
I have 2 sollutions (1 CMS, 1 Customer specific with controls). The customer controls are coppied (with xcopy) to the CMS location. In the web.config of the CMS the specific controls are registered.The controls are useing functions from the CMS dll as well.How can I debug those two solutions as it where only one? I tried to start the CMS in debug mode with breakpoints in de CMS and customer controls, in this case only the breakpoints in the CMS are used. If I run the customer controls in debug mode only the braekpoint in this solution are used.The CMS is running on my local IIS 7.