Classic ASP.net not loading in visual studio - asp.net

We have this old ASP.net website which requires some basic link updates and to place some hard coded images aside from our CMS.
Now i downloaded the entire website from the FTP to load up and test on my local machine.
But when i tried loading it in visual studio it loads perfectly, but when i try to start the website to test if its loading it does not load in my browser.
After that i started googling away looking for solutions, but i did not find any that worked for me.
I attached an image with the problem im facing, i hope someone can help me.
Thanks in advance.Error

Related

MS Visual Studio 2017 problem with ASPX publishing a website

I'm quite new in ASPX development, as I was a desktop application developer for the past 18 years.
I am creating this ASPX / VB.NET application and when I build it and run it shows all the changes I did without any problem, but when I publish it shows the results in the attached picture.
Could you please help me by guiding me in the right settings and I will be very much appreciated?
Thanks in advance.
You are running the application from IIS? Set default page to view to your required page.

Windows Authentication 401.2 Error using IIS Express

I'm having a hard time fixing an error that I currently have and I hope you can help me with it.
I am developing a little ERP-WebSite that is going to be used within an intranet. Naturally I want to use Windows authentication to make it as comfortable as possible for the user. I developed the Website using Visual Studio 2008 and its integrated development server. Recently I migrated to VS2013 and .NET 4.5. Code wise everything went good and I am able to build everything but here comes the problem. Because I am using VS2013 now I also have to use IIS Express. When I try to debug the Website i receive a 401.2 Error. Error Code 0x80070005. On VS2008 everything worked perfectly and I am 99% sure I have the IIS config set up currectly. Here are the relevent parts:
applicationhost.config:
I also set the according values in the Project Settings in VS2013.
I'm kind of lost right now. Any help will be much appreciated!
EDIT--------------------------------------------------------------------------------------------------------------------------
After playing around with IISExpress for way to long now, I finally got it to work again. Something must have been wrong with my previous eddits of the applicationhost.config file of the IIS Express. I just deletet it and let VS13 recreate it. Afterwards I was able to run my site using IISExpress. I hope this might help someone who has the same problem as I do. Sadly i realized that it is painfully slow. It takes almost 2 minutes for some pictures to get loaded etc.. What could be the cause of that ? I also tried using the full IIS Version (with Win-authentication installed) but when I run my site using the local IIS I receive an XML-parsing error: No element found. Using the local IIS would be a lot faster than using IISExpress, so I'd very much like to fix this Error.
Thanks for any help in advance.

Old Asp.Net Web Site Project - No Project file?

So I have an Asp.Net website that i'm responsible for. I'm having a build issue, that as far as I can tell, may be either MacAfee or some other random cause.
But thinking back, I want to say the problem started when I added a "Test.aspx" form to the site, did some testing, then removed the Test.aspx form from the site.
I'm using TFS 2010 as my source control as well. Which I don't know if it applies or not.
My question is, is there some hidden location where all files to be included in publishing a website is maintained?
Is there a Project file for a Web Site app and if so where is it?
I've built the site using MSBUILD and notice some metaprj project file in the output but I can't seem to find any such file.
Web Site apps aren't meant to be built into a dll file. There is a conversion wizard to make it a web project but it doesn't always work well. My advice would be to continue to work with it as a Web Site app. The code files are compiled at at runtime on first use. You can run from Visual Studio or setup a site in IIS. Nothing is hidden in a Web Site app and there is no project file. So, you shouldn't have a build issue because you shouldn't be building. Try to run the app as is and if you get an error let us know what the specific message is.

Accessing remote Umbraco website from Visual Studio

I'm about to deploy a site where some functionality is omitted to get the website launched as soon as possible. This means that after the site has been deployed to a live server, some development still needs be done.
I have mainly been used to working on local projects, and have just been playing around with opening the site as a FTP project in VS2012.
This seems to be the way to go, but unfortunately, IntelliSense doesnn't play nice (not all namespaces are recognized) and when re-building the project, it seems as the whole Umbraco project is recompiled (which creates an enormous overhead). And I have not found a way of excluding Umbraco specific folders from the project.
Another thing is that the project is recognized as a WebForms project and not MVC4, for which I would also like a fix :)
Any suggestions on how to carry on from here? Suggestions and best practices is very welcome!

CSS problem between Visual Studio IDE and IIS

I'm not a web developer, so what seems weird to me is hopefully an easy one.
Have an existing ASP.NET web site which I need to modify, using VS 2008. I worked on an aspx page and somehow the CSS settings changed and messed the page up badly. I restored the old CSS files and now the page is fine again in the IDE but still a mess when I run the project.
Any ideas would be much appreciated
Steven Segal
Have you tried clearing your browser's cache?
Could it be, that website needs authentication (i.e. FormsAuthentication) ?
If so, the Visual Studio ASP.NET Development Server also blocks css files and images making your web app look like crap in Visual Studio... IIS however doesn't have this behaviour, so when you deploy your site, all looks nice and tidy...

Resources