We are developing web site .net core 2 in Visual Studio 2017. That web project was working fine.
Now I try to
Start Without Debugging (Ctrl+F5) get an error: Site Can't be reached. ERR_CONNECTION_RESET
How can i resolve this?
image description here
I think you might not have the right IIS settings installed. Take a look in your windows features. Make sure you have support for the right version on ASP.NET turned on which are available from control panel.
setting you may have like this
you can check official document here
I figure you probably won't have the correct IIS settings introduced. Investigate your windows highlights. Ensure you have support for the correct form on ASP.NET diverted on which are accessible from the control board.
setting you may have this way
you can check the official archive here
Related
I have a project on VS 2019 Windows machine that is fairly small but containing Web Forms. I have taken the whole project folder zipped it and loaded it in directly to JetBrains rider on the Mac. Here is what it looks like currently.
1 Errors on solution
2 What the error says on every web form page
It appears that the System.Web.UI is not accepted on the Mac.
I have looked all over and the forums are telling me to download a package that proceeds it. This does not exist either. How do you replace the System.Web.UI?
WebForms are out of date and cross-platform of the web form is not impossible, but you will need to take into consideration everything that is used on the master page. It is not only a problem with MAC but any other IDE other than Visual Studio. You are better off migrating to the MVC style, it may take time but it appears to be the industry standard. WebForms are supported in Rider, however, you must manually create all the pages that belong with it like the master, and ensuring the routing is the same. Also, it seems to be severely difficult to connect an MVC application with WebForms. You would have to create the same exact style with _layout.cshtml and Site.master page. Seems like an outdated process that works if you want to just make forms.
First time trying to install Umbraco. I followed the instructions on how to install Umbraco 8 with NuGet. (https://our.umbraco.com/documentation/Getting-Started/Setup/Install/install-umbraco-with-nuget)
But I'm having issues with getting the Umbraco installer to show up. After starting without debugging (Ctrl+F5) I just get the Chrome error page for ERRCONNECTIONRESET. It does seem some resources are missing in my project solution. Tried cleaning and building the solution over and over, but no luck.
I'm using Visual Studio 2019 16.9.3 with .NET Framework 4.7.2 (also tried it with 4.8)
Thanks in advance.
Please take a look at Paul Seal's video about how to install Umbraco v8, hopefully, this will help you do your installation successfully.
PS: From the error message you have shared, I can't be sure what is missing but if you follow Paul Seal's steps, which are the default Umbraco installation steps, you should be able to create an Umbraco website.
The issue was that Visual Studio navigated to the HTTPS variant. When I navigated to the HTTP variant, it works.
Recently, Visual Studio 2013 started hanging again when trying to debug/trace an ASP.NET web site. The site was created with WebMatrix 3 but I don't think that is relevant.
VS2013 opens the web site Solution. It takes a really long time to load up. Once it does load up and I run the project, it hits my first breakpoint and then the IDE Window quickly shows "(not responding)" in the title bar and the IDE is now hung.
This happened to me a long time ago and the root cause was needing to set the "use 64-bit IIS" option as indicated by this SO post:
Visual Studio 2013 crashes and restarts every time I run my test solution
But I triple-checked and I do have the 64-bit option checked. What can I do to fix this?
What worked for me was resetting visual studio. I got the suggestion from http://www.vosseburcht.com/?p=69
See this blog in the issue. It basiclly says to make sure "show all files" is selected in the solution and check for any folders that don't belong that are not part of your project/solution.
The problem resurfaced again a few days later and I finally figured out the problem with my uncooperative debugger. I have a folder containing approximately 20,000 images that are not included in the Visual Studio web project but are sitting in a directory in the web site. I had turned on "Show All Files" in Solution Explorer to add some script files into the project. When "Show All Files" is off, F5 (Start Debugging) works like champ. When "Show All Files" is on, Visual Studio becomes unresponsive. In reality it is not "frozen" but simply taking a very long time to process those 20,000 image files.
For me, it was a folder created called backup, which was a backup of the site (created by VS). I deleted the folder in question and the site loaded for debugging.
It might be caused be some extensions in Visual Studio, I was facing a similar problem when degbugging asp.net websites. Try running VS in Safemode: devenv.exe /Safemode. In my case it was caused by Multilingual App Toolkit extension, after uninstalling it, debugging ASP.NET websites works once again.
In my case, I was able to solve it by running it as an Administrator!
Don't know why, couple of days back it was working fine, suddenly it started to freeze when trying to debub web app!
Hope it helps someone!
BTW: I am running VS2013 Ultimate, with Update 4
In my case it's the IntelliTrace that causes problem. I need to disable it https://msdn.microsoft.com/en-us/library/dd264948(v=vs.100).aspx
I have the same situation and "solved it" in a very particular way: Rebuild the solution and run it without debugging (Control + F5), then go back and debug it the normal way.
I was having a similar issue, and I found the following error in Windows Application Event Log that corresponded to the problem:
Application: PowerShellToolsProcessHost.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Runtime.Serialization.InvalidDataContractException
...
So I removed PowerShell Tools for Visual Studio extension, and the issue went away. I am using Visual Studio Ultimate 2013 Update 5.
I had this problem while writing an Excel add-in.
Not being a web app I was pretty sure that checking the 64 bit IIS Express option would make no difference, but it did!
I have no idea why, but it runs in debug ok now :)
I had to install Windows Management Framework 4.0
My solution was to remove all the .bak backup files generated by DevExpress ProjectConverter when I had upgraded to the new DevExpress version.
I have a c# class library that I am calling from Classic ASP.
Is it possible to debug this using visual studio? Break points in the class don't work, which isn't surprising.
I am running this on iis7 in the browser, rather than through Visual Studio 2010 because of the fact that I'm using a classic ASP page. Do I need to get this running in Visual Studio in order for this to work?
I also tried to use Response.writes, but they result in:
The name 'Response' does not exist in the current context
You need to attach the debugger to the process (either IIS or another debugger that you are using to debug your classic ASP application) that is loading the assembly.
Under VS2010 go to Tools -> Attach to Process (probably the same under 2008 as well).
try to add in the code of the lib: System.Diagnostics.Debugger.Break(); where you want to break. Also ensure the lib is compiled and deployed with the pdb symbols. When the code will reach the instruction, IIS will throw an exception. The system will ask you to attach a debugger, and you're on the way.
I actually wrote an article regarding this:
http://www.jameswiseman.com/blog/tag/visual-studio-2010/
From the article:
Open Visual Studio 2010
This is easy enough if you have it installed. Might be a bit tricky if you don’t ;-)
Open your website in Visual Studio
Again, easy enough.
Fire up your web site.
I.e. open your browser and navigate to the website.
In Visual Studio, click ‘Debug’ Menu -> ‘Attach to process’
You may need to tick the box labelled ‘Show processes from all users’
‘Inetinfo.exe‘ if application protection is low or ”dllhost.exe‘ if application protection is higher. You may get an ‘Attach Security Warning’ popup. If so, continue On. It’s a bit scary at first, but if it’s your own app on your own PC, then you’ll be ok.
If you’re worried about this, follow the advice on MSDN.
Add a breakpoint to your code, and navigate to a location where you will hit it.
Troubleshooting - Registering pdm.dll
This worked on the first occasion that I tried it. Subsequent attempts were not so successful, and I found a few things that I had to do.
When trying to attach to ‘Script Code’ I got the following warning in the IDE.
Warning: Cannot debug script code. The
correct version of pdm.dll is not
registered. Repair your Visual Studio
2010 installation, or run
‘regsvr32.exe
“%CommonProgramFiles%\Microsoft
Shared\VS7Debug\pdm.dll”‘.
Just follow these instructions.
Troubleshooting - Restart IIS
This also helped on one occasion. Can’t really say why.
You will make your life much easier all round if you wrap you .net classes in a web service then call the web service from the classic asp pages.
For debugging, attach the debugger to the process as described in other answers.
For tracing, I find very handy the combination between System.Diagnostics.Trace.Writeline() in the class library and an OutputDebugString listener like DebugView.
Microsoft Visual Studio 2008 Service pack 1 comes with Visual Basic Powerpacks which has the DataRepeater control.
I used this control in my c# winform application. in my system everything is running fine. now i copied the debug folder to other system which has only .Net Framework 3.5 SP1 installed. in this system is giving me error cannot load dependency Microsoft.VisualBasic.PowerPacks.dll even i set the Copy Local to "true" for "Microsoft.VisualBasic.dll" and "Microsoft.VisualBasic.PowerPacks.Vs.dll"
please tell me how to solve this problem
on this page is the information you are looking for: [http://blogs.msdn.com/b/vsdata/archive/2009/12/29/visual-basic-powerpacks-is-released-in-visual-studio-2010-beta2.aspx][1]
i have had some bad experiences with the "Visual Basic Powerpacks" so if possible I woud try to avoid using it.
best regards