Last post Jun 21, 2013 03:22 PM by gbdarren
Feb 27, 2007 03:01 PM|sarahyh|LINK
I have a project created from New -> Web Site in Visual Studio 2005.
When I try running the web site, i get the following ArgumentException.
"Culture name 'sources_app_code' is not supported. Parameter name: name"
But the program runs fine.
Anyknow know why this exception occurs?
Mar 01, 2007 02:07 AM|vivek_iit|LINK
Are you using localization in your project? It seems the problem is with the setting of locale of the current thread.
Mar 08, 2007 03:22 PM|sarahyh|LINK
Well, I'm getting lots of "A first chance exception of type 'System.ArgumentException' occurred in mscorlib.dll" messages in output window.
(with the error message: Culture name "....." is not supported)
They are thrown because of .svn folder in App_GlobalResources.
If I remove .svn folder, those exceptions are gone.
Is there any workaround for this problem other than removing .svn folder?
Or can these exceptions be ignored safely?
Mar 08, 2007 10:57 PM|vivek_iit|LINK
It seems you are using SVN source control and having problems with the hidden svn folders which maintain the state of files locally. I have read that ASP.NET web projects have issues with .svn folders and you might need to rename these folders. Check out
Hope this helps,
Apr 18, 2007 11:42 AMemail@example.com|LINK
I am getting the same error too, and I am running VS 2005 (one of the articles linked to on this post said that "this problem" was fixed in VS2005.) The error happens right when I start my web application. Here is some more information on it:
Message="Culture name 'sources_app_code' is not supported.\r\nParameter name: name"
at System.Globalization.CultureTableRecord..ctor(String cultureName, Boolean useUserOverride)
I am not sure what "SVN Source Control" is, we are using TFS here. Also, I only get the error when loading the first time - ie: if I kill the application and then restart it, the error does not happen. BUT, if I kill the application AND the ASP.NET Development
Server - it will happen when I restart the application.
Jun 19, 2013 03:06 PM|gbdarren|LINK
Did you ever solve this issue? We are having the same issue and would love to know how to solve it.
Jun 21, 2013 03:22 PM|gbdarren|LINK
Deleting the .suo file (Visual Studio Solution User Options file) fixed the issue for me.
This issue came up when I upgraded from .NET 2 to .NET 4 for the project.