We Keep Coding

Web app showing different screen at visual studio and Azure

I am maintaining an app, developed by someone else who is not in the organization anymore.
And my skill with .net is very limited. (Can run and deploy the code.)
As you can see in the image, the same code and same database it works fine in visual studio, I can see the table with columns. But the deployed code in Azure is not showing the table.
Just want to check with experts here, if you see anything obvious missing here?
Just a bit of background about the above Table: It is a dynamic table, Admin can customize the table columns, width, etc.
Apologies for the silly question, but just trying if I can get a quick win by asking it here.
Cheers David

This could be due to a runtime issue, which occurs when the files in your wwwroot folder are precisely what they should be, but the site doesn't function correctly for some reason, such as a missing element, or it could be due to a change in how the page is viewed.
After you've deployed, check your Kudu Console to see if the View of the controller you're deploying has changed.
I tried reproducing the same and this is how I compared my Kudu Console.cshtml and VS Code.cshtml files.
Here is the output

When I ran in inspect mode found some of the .js files were showing 404 error.
Checked the visual studio and for some reason, those were not added to the project!!
So I had to manually include them in the project. After publishing it is now working fine.

Visual Studio Web Apps Publish fails - no errors

I have several ASP.Net web form apps in a Visual Studio project. In one of the apps, I was working to add a test page for some additional features we wanted to test before adding to our main pages. Afterwards however, I was trying to publish to our server, but keep getting a message box saying: "The publish has failed due to one or more errors.".
Build succeeded Image
Publish Failed Image
I checked the errors, but none are given. The build was successful and other then a few un-used references, there are no other indicators on what the issue exactly is. We have a few other projects that normally allow for publishing without issues. So I don't believe the issue is from Visual Studio, but I am not completely sure. I'm using Visual Studio 2015 version 14.0.24720.00

Figured it out!
There is a Thumbs.db file that was auto-generated in the images folder. I decided to go through the output window line by line to see if I could identify where the publish was failing at. I noticed a line that said the /Images/Thumbs.db file could not be published and that access was denied.
Doing some more online investigating, I found some other questions along the same line as the premise for this one. Specifically the question here was most helpful. Tammy Spencer's (#user:973679) answer to try and delete the file was what made the publish succeed. So thank you Tammy.
In addition, the Thumbs.db file wouldn't let me delete it at first. But after doing some more searching, I found this YouTube video that made the file deletable.

VS2017 How to create an Empty Web "Application"

I cannot find a way to create an Empty Web application in VS2017(ASP.NET WebForm).
In VS2015 there was a template for this.
Seems like VS2017 can only create Empty Web Site.
This is what I have :
==============================================
Update for the whoever see this post in future: I Ended up rebooting my computer AND VS2017 did some updates. After that, The Empty Template appeared! Clearly a VS 2017 bug.

Go to File > New Project
This will prompt you to the following Dialog where you choose for a Web App.
Then you will get to the point where you can choose a template

update Web/Services References not working

I am trying to update my Web/Services References from VS and going on App_WebReferences and right-click go to Update Web/Services References. No files are open in my Visual Studio. I open it by using File/Open Web Site and the name of the web sites.
Here is the error I got. Failed to update Service Reference "CarServiceReference.Reference." Error: Unable to connect to the configured development Web Server. Failed to register URL
"http://:...." for site "CarDealer" application "/". Error description: The process cannot access the file because it is being used by another process.
Any idea on how to get over this error ?
Thanks for any propose solution

Like Sixto Saez said, I shut down Visual Studio and re-open it, choose my Web Solution and then I was able to Update the Web/Services. Thanks

Unable to automatically step into the server. The debugger failed to stop in the server process

I receive the following error when attempting to Step Into a process using F11 in Visual Studio 2008 Team System:
"Unable to automatically step into the server. The debugger failed to stop in the server process."
I have searched pretty long and hard on the internet and the most relevant message I found was http://msdn.microsoft.com/en-us/library/65004e38%28v=VS.90%29.aspx. Unfortunately, this did not help. All signs are pointing that my ASP.NET setup is incorrect, but it's the IIS environment that ships with VS2008 Team System so I didn't make any figuration changes.
The answer to this question, which sounds like it might have fixed my solution is no longer an active link: Unable to automatically step into the server when debugging WCF. Does anybody know how I can jump into and fix this problem?

This took me 3 days and no less than 5 people looking at the problem to solve; although I'd like to report the exact problem I'm still left to speculate. However, I am no longer getting this error when I do the following:
I opened the .cs file of the base class my service derived from within my Testing solution. I set a break-point in the constructor of this base class. Because the base class wasn't within the solution of either my web service nor my test solution (it was simply referenced), VS2008 was unable to break into this .cs file.
The solution was rather moronic. I opened the base class.cs file within my Testing solution (the file only, not the solution). I set a break-point in the constructor class, and I was then able to step-into all other files from there. Once I was able to successfully set a break-point and stop the debugger in the base class within my actual Test solution, I was able to continue debugging as I would normally expect.
My only conclusion to the root cause of this problem is that VS2008 is retarded. I'm sorry it's not much of an answer, but this is how I was able to resolve the issue which sunk over 30 hours of time.

This could be because the debug not reaching to your break point there may be some error occurring before it.Try add break point in the base class constructor.

I know this is an old question, but I encountered a similar issue and the problem was that I was in Release mode rather than Debug mode. Changing to Debug mode solved the problem. I'm using VS 2010.

this problem can occur if you have another solution opened and running (another instance of visual studio).

I got this error once when I had the wrong project set as the startup project in the solution.

This same thing happened when I had the service open in a browser. I closed it out and it fixed the issue.
Guessing you have it open multiple times. (basically repeating what Avicena00 said)

I got this error when trying to import a file that was too big. I had to increase the maxAllowedContentLength value in my requestLimits area in my web.config to fix it.

As stated this is an old problem, but I ran into it running later versions of Visual Studio, and have not seen the solution that I found listed. This problem in my experience happened when the service was using a lower version of .Net (in my case 3.0 vs 4.5). Changing the .Net version int he project properties to 4.5 (which matched the project referencing the service), solved my problem.

This worked for me: Tool > Options > Debugging > Use Managed Compatibility Mode
Visual Studio 2018 Options

In my case the problem was that I had open the same project and its copy (in different directory) in two Visual Studio instances. Solution than in final was simple as closing all IIS instances of Web projects and closing all instances of Visual studio. After opening just one project at a time debugging started to work like a charm.

I get this error when I debugged one and another solution.
The answer is very simple
Click on the solution->Properties->Multiple startup projects
Then select projects and click f11.