A Little Background:
My team has a somewhat outdated ASP.NET MVC solution that I have been tasked with upgrading as current as possible. We're migrating up from MVC 2 and WebPages (ASPX/ASCX) to MVC 4. The solution is rather large (20+ projects) and most of it is working properly. We have run into an issue though where some of the aspx pages throw the compiler error:
> "BC30456: 'InitializeCulture' is not a member of 'some_extended_view_name_here'...
Most of the digging I came up with on the issue recommends that when publishing, you unselect "allow this precompiled site to be updatable". Problem is that when running locally via the "Run/Run Without Debugging" buttons, you aren't publishing per-se. So...
TL/DR: Is there any way to change the 'publish' settings when using the run or run w/out debugging buttons for MVC websites in Visual Studio 2012/2013? I have looked and looked, but can't find anything suggesting it's even possible.
Related
Using Visual Studio and Chrome I have recently started debugging a website at http://localhost:50481 in a project created with the ASP.NET empty website project template. About the same time I noticed that my desktop banking website was running very slowly. In fact the whole https://www.targobank.de/de/index.html web site runs very slowly using Chrome. All other websites are fine. In MS-Edge the targobank site runs fine (sometimes). I believe that the Visual Studio setup is somehow slowing Chrome at my German bank!
Does anybody know why this might be happening? Perhaps other users with similar VS configurations could try the website.
Here is some more detail on my VS setup. In order to use the ASP.NET empty website project template I had to install "Additional project templates (previous ver..)" as shown below and as recommended on the excellent stackoverflow.
Use the ASP.NET empty website project template thus
and then debug my Javascript in Chrome using a website at http://localhost:50481.
Which version of Visual Studio can be used to open a project which is built as ASP Web project
I have Community edition 2019 Does this support ASP projects?
I know these days no one is using ASP for building web apps The purpose is to maintain an existing ASP solution for a couple of more months 9If any bug fix requests from the client comes ) and start to build a new project using the latest version of Microsoft technologies
Visual Studio
Most versions of Visual Studio support editing Classic ASP code, couple of things to keep in mind though.
Frontpage Server Extensions is no longer supported, the best approach is to use a mapped drive or better yet store the code in source control (Git, SVN etc.) and work with the code locally (can bind to a local instance of IIS).
The IDE can be quite cumbersome for working with Classic ASP as it's designed for more modern technologies.
It also has sophisticated debugging through the IDE via the "Attach to process" which will work with Classic ASP running in IIS as long as the web application has been configured correctly for debugging. See How do you debug classic ASP?.
Visual Studio Code
Another option is Visual Studio Code which is a free IDE built on the principle of open source projects for cross-platform. It's becoming a popular free IDE for many developers rivalling the likes of Atom, Sublime etc.
It's lightweight and extensible through extensions, there are already some useful extensions for Classic ASP including this one;
Name: Classic ASP Syntaxes and Snippets
Description: Classic ASP Language Support and Snippets from tmBundle
Publisher: Jintae Joo
It also has built-in support for popular source control solutions like Git and more powerful available through the extension marketplace that is built into the IDE. If you do use Git would recommend installing the GitLens extension.
Every version of visual studio since I started with 2010 (was there something before it?) handles Classic ASP just fine. I'm on VS2019 right now.
I even have a project which is a combo Classic ASP, Webform, and MVC all in one project, with some session sharing, and I routinely code and debug in all. The only limitation is that when you debug, you have to choose whether you're debugging Managed code or "script".
With each I "attach to process" and choose which code I want to debug. Classic ASP debugging is fantastic, and I can't believe more people don't do it. I see basic questions on here which would easily be fixed with standard debugging techniques (settings breakpoints, evaluating variables).
The ONLY thing which isn't supported is code formatting inside <% %> blocks. If I ever get some time maybe I'll make an addon for it.
I am following this setup tutorial
https://docs.asp.net/en/latest/tutorials/your-first-aspnet-application.html#create-a-new-asp-net-5-project
And have come across a problem. In the tutorial the instructions are as follows:
Start Visual Studio 2015. From the File menu, select New > Project.
Select the ASP.NET Web Application project template. It appears under
Installed > Templates > Visual C# > Web. Name the project ContosoBooks
and click OK.
This is fine, but in the next step :
In the New ASP.NET Project dialog, select Web Application under
ASP.NET 5 Preview Templates. Also, make sure the Host in the cloud
checkbox is not selected and click OK.
I am seeing no ASP.NET 5 Preview templates!
The only thing I am noticing is that my Authentication states No Authentication but I am signed in so I am not sure what this means or whether or not this is a factor.
The version I have installed of Visual Studio is "Community 2015".
I have already gone through the perquisites as outlined in This Article.
I am hoping that someone with a more thorough knowledge on the topic can help me out as I have not been able to find any threads etc. of the same issue or what could be causing the Templates to be missing.
Asp.net 5 templates no longer exist - they are renamed to Asp.net Core: ASP.NET 5 is dead - Introducing ASP.NET Core 1.0 and .NET Core 1.0
So, when creating your project, instead of picking "ASP.NET Web Application" as it is in the video - you would select "ASP.NET Core Web Application" and then on the next page those 3 templates (Empty, Web API, Web Application) are the same as the video's asp.net 5 preview templates
VS 2015 Preview is going under ASP.net Core web application. If you cant see that one under templates you may go to this site and download .NET Core 1.0 for Visual Studio then install.
I have concluded, by following another stackoverflow question on How to check the ASP.NET version loaded on a system as I noticed that the templates were categorized in the ASP.NET versions (4.6.1 & 5) in the tutorials but mine were not.
So I then checked and my files in C:\Windows\Microsoft.NET\Framework are as follows
Revealing no v5.0 directory. I rectified this and now all of the templates are available
AMENDMENT:
To fix it:
I went to http://www.asp.net/downloads and downloaded ASP.NET MVC 5
I ensured I had Developer Tools checked in the download process.
This issue was now resolved - As I then had the MVC 5 template files. Because I downloaded them, so I had them... and no longer didn't have them.
ALTERNATE FIX:
Furthermore From my research, some people had not included Developer Tools. To resolve: go to old mate 'Add or remove programs' and find your Microsoft Visual Studio 20xx install, 'change' and install Microsoft Web Developer Tools
I have had the same problem but it is actually even better because "The new dialog enables you to change the default authentication options for many of the templates. For example, when you create an ASP.NET Web Forms project you can select any of the following options:
No Authentication
Individual User Accounts (ASP.NET membership or social provider log in)
Organizational Accounts (Active Directory in an internet application)"
check out this >> http://www.asp.net/mvc/mvc5
I recently had this problem and finally fixed it by uninstalling (control panel -> uninstall a program) Microsoft.NET Core and Microsoft Visual C++ redistrutable 2015 (x64 & x86) and then re-installing the asp.net core rc2 (https://www.microsoft.com/net/core#windows or possibly check Tools->Extensions and Updates->Updates inside of Visual Studio).
I uninstalled the Visual C++ redistrutables because I kept getting an error when trying to re-install asp.net core rc2. It kept telling me that it already existed even after I had just uninstalled it and the update was showing in the "Extensions and Updates" section of Visual Studio after trying (but failing) to install the asp.net core rc2 update.
before posting, I read all the posts related to this query, as well as the ones in asp.net forums. There is a filed bug related to this problem which was filed as solved, but still unsolved in the current version (VS2013.4).
The problem is that my Visual Studio 2013 is missing the "Add Controller" option, so I have no way of scaffolding new controllers in my MVC 5 projects. Some clarifications:
It is a new MVC5 project, not MVC4->MVC5 migration.
Updated all nuget packages, all VS related stuff as well.
Repaired VS2013
Uninstalled, rebooted and reinstalled VS2013
Upgraded it
Installed the .NET Web Tools from the DVD and from internet.
Changed the project GUIDs as some suggest (btw, those solutions seem to work only for MVC4 or less, not for VS2013 MVC5)
I have a virtual machine at work with win8.1 64bits and VS2013.4 that does have "add controller" option (same config as my home laptop, but in a virtual machine). Also tried to copy the same .csproj settings with no luck.
So, basically, unless someone came across another solution I still may have not tried yet, is to format and reinstall everything.
I don't know if this is applicable to your case and if it will directly help you, but I had some problems with Microsoft development tools and hidden buttons when using them on my touch screen enabled laptop
The solution was to turn off windows/controls scaling in Control panel (set it back to 100%)
We've been working on an application that quite heavily relies on VirtualPathProviders in ASP.NET.
We've just come to put the thing on a live server to demonstrate it and it appears that the VirtualPathProviders simply don't work when the site is pre-compiled!!
I've been looking at the workaround which has been posted here: http://sunali.com/2008/01/09/virtualpathprovider-in-precompiled-web-sites/, but so far I haven't been able to get that to work, either! (Well - it works fine in visual studio's web development server - just not on our IIS box - again!).
Does anybody here have any more information on the problem? Is it fixed in .NET v3.5 (we're currently building for v2.0)?
Unfortunately that is not officially supported. See the following MSDN article.
If a Web site is precompiled for deployment, content provided by a VirtualPathProvider instance is not compiled, and no VirtualPathProvider instances are used by the precompiled site.
The site you referred to is an unofficial workaround. I don't think it's been fixed in .NET 3.5 SP1