Blazor WASM projects will not run - blazor-webassembly

Creating a new Blazor WASM project will not run using dotnet run or Visual Studio non-debug mode. It will run in Visual Studio debug. Blazor server works properly. I do my development using VS debug mode, so I have no idea how long this has been broken.
The browser tools shows an exception while running WebAssemblyHostBuilder.CreateDefault(args); in Program.cs
Exception: System.TypeInitializationException: The type initializer for 'System.UriParser' threw an exception.
Any ideas? I am really stuck on this!
Thanks
I have tried reinstalling .NET sdks, Visual Studio, but am unable to fix this.

Well, don't I feel like an idiot. I spent all this time trying to fix the development environment, and in a last act of desperation, I tried a repair on the Edge browser...and that fixed it.
Sometimes it is better to be lucky than good...

Related

Migrate old VB.NET project from VS2013 to VS2017

I have a huge enterprise asp.net application that perfectly builds and runs on servers. We've been using Visual Studio 2013 in our workflow. Now we want to migrate to newer IDEs. But if I build this application in Visual Studio 2017 I'll get this error.
Error BC40004 sub 'PreInit' conflicts with event 'PreInit' in the base class 'Page' and should be declared 'Shadows'.
I think it's a problem with VB compiler version (again vs2013 builds project). Do you have any idea how to fix this?
My solution contains 40+ projects. The main project is asp.net webforms app written in VB.net. Other projects are services and code libraries written in C#.
I tried to specify VB.net version in .vdproj manually. But it didn't solve my problem.
edit: Fine. Thank you all for your responses. I got that problem is about code and that visual studio analyzer has changed a lot in the last few years. I'll try to find out the reasons why this code have been working without exceptions.
BC40004 is a warning, this shouldn't prevent you to compile the solutions unless you set the Treat warnings as errors on the project's property under the tab compilation.

Debugger For Visual Studio is not Working

I am facing a very serious issue with visual studio debugger. My asp.net application is hosted on local IIS server. Yesterday i was debugging my code suddenly it stopped working. I verified w3wp process. It was same as IIS process. Then i tried to download symbols but i am not sure either they are all that i need. I tried attaching debugger on visual studio 10 and visual studio 12. Neither of them is working in this case. I tried to attach debugger of JavaScript but it is also not working.
Please Help.
Are you building full debugging symbols? If not then the debugger has no information to relate the source code to the in memory activity under the debugger. This is set in the project properties per configuration.
Also ensure the symbols are in the bin folder.
You can validate that VS is loading the right symbols with the Debug | Modules window.
I cleared temporary cache of .NET Framework. then i again deployed my application on IIS with different name and magically everything started working.

"An operation is not legal in the current state" error when trying to launch ASP.NET project in VS2013?

I have an ASP.NET web site created with WebMatrix 3. I do have the option in VS2013 checked to use the 64-bit version of IIS Express since I am running on 64-bit Windows 8.1. When I try to launch the project I get the error "An operation is not legal in the current state". Does anybody know how to fix this?
I got this same error "An operation is not legal in the current state" when running a project on Google Chrome, Stopping the project then closing all chrome instances fixed the problem.
I think it's related to visual studio not being able to attach to chrome instance for debugging.
Closing Chrome and restarting IIS (e.g. in IIS Manager) should solve the issue. It helped in my case.
Just had the same issue on VS (Visual Studio) 2017 this morning.
The steps that will resolve this are:
Stop project that runs in VS
Clean all IIS instances that VS temporarily created
Compile project and start that service again

Compiling ASP.NET

I'm compiling ASP.NET code for the first time ever and I'm stumped.
I downloaded MINGW-Get and just finished installing it. The client gave me the source code and I found a file called RSConfig.exe.
So I assumed that was the config file, ran it, and then tried "make" but got the error
No targets specified and no makefile found. Stop
Any idea what I'm supposed to do? I don't see anything that would resemble a makefile in the source code.
Thanks in advance!
Do yourself a favour and install Visual Studio Express:
http://www.microsoft.com/visualstudio/en-us/products/2010-editions/express
It makes development easier and fast
It sounds like you might want to get familiar with the background concepts around asp.net and it's defacto development environment Visual Studio (there are many versions of visual studio).
As Andrei recommends, using Visual Studio Express is a good free way of getting started. The version most suited for web development is Visual Web Developer Express.
Attempting to compile .net code from a toolset such as MinGW isn't a typical route for using asp.net, however I've not used MinGW before and not sure it's possible to compile .net code from it.... Although it is perfectly possible to compile .net code from the command line (using the .net framework sdk) , I certainly wouldn't recommend it if you are getting started.
I'm going to make a guess that it is an ASP.net web forms project, it being the most prolific asp.net project type at the moment.
This official asp.net site http://www.asp.net/web-forms will guide you through what web forms are and how to get the development environment setup. Having this sort of background will aid you in solving your particular situation.

Problem with debugging ASP.Net application on IIS 7 on Windows 7

Few weeks ago I started using VS 2008 (Professional) with Windows 7 (Enterprise).
When working with ASP.Net web applications I repeatedly stumble over the following error:
After opening a solution with a web project the first compilation and debug go perfectly fine. The second time I try to debug the solution I get the "Unable to start debugging on the web server. System call failed" error and solution does not start at all. When I try to debug it again it always shows the same error but sometimes the app actually starts but does not break on the server code at all.
Any ideas why this could happen?
Thanks a lot for any suggestions.
(I use local IIS and run VS as Administrator)
Have you installed SP1 for VS 2008? I am using Win7 as well, and alot of the issues get magically resolved with a service pack. HTH.

Resources