Home > Value Cannot > Value Cannot Be Null. Parameter Name Virtualpath Asp.net

Value Cannot Be Null. Parameter Name Virtualpath Asp.net

When the module loads up, I call a subroutine that loads the appropriate control based on a session variable. I also have a very simple ASP.NET site I am using to test with. The common factor is definitely the application pool being recycled. Does Intel sell CPUs in ribbons? check over here

That would probably help a lot, to know which method, specifically, is c ausing the error, and which of your methods is calling it. Back to Top 12 Next .NET TOOLBOX DevCraft MOBILE APP DEVELOPMENT Telerik Platform DIGITAL CONTENT & EXPERIENCE Progress Sitefinity SOFTWARE QUALITY Test Studio Get Products Free Trials Pricing Solutions Enterprise Partners I just update all the nuget packages. Tervel Admin 1337 posts Posted 13 Aug 2009 Link to this post Hello Jay, We still have not been able to isolate the problem in a sample application - not even

regards, peter  Fiko Admin 1406 posts Posted 13 May 2009 Link to this post Hi Peter, In this case, could you please try to isolate the problem in a simple project List statusMessages = new List(); bool errorOccurred = false; // Check for "page" or "sort" in QueryString so that if the visitor // clicked "Next" or "Previous" or a column header share|improve this answer answered Nov 16 '14 at 6:06 odyth 2,86022233 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign Exception Details: System.ArgumentNullException: Value cannot be null.Parameter name: virtualPathSource Error: An unhandled exception was generated during the execution of the current web request.

Parameter name: virtualPath Source Error: Line 163: