I use Visual Studio Folder Publish option to publish my Web apps to my IIS server. They are mostly ASP.NET Core 2.0 apps. Before I updated Visual Studio 2017 to the latest version my published web app would look like this in the IIS Site folder: (picture below)
Now that I have updated Visual Studio 2017 to the latest release of 2017, my Core 2.0 apps site folder has tons of files, like this:
I am not sure why, obviously nothing has changed with my app project files that I know of. I also noticed when I publish a newly created ASP.NET Core 2.1 web app, it only publishes the short list of files.
Does anyone know why this happens and if it is possible to fix (or even worth fixing). I haven't noticed any performance difference but my apps are not very performance intensive.
Related
Just installed Visual Studio 2017 – Enterprise Edition with the following workloads:
Universal Windows Platform Development
ASP.Net and Web Development
.Net Desktop Development
.Net Core cross-platform Development
After this installation, when I create a new .net core or .net standard project, the visual studio restarts while loading the project template.
Steps to create the behavior:
File ⇒ New Project ⇒ .Net Core ⇒ Asp.Net Core Application (.Net Core)
Visual Studio tries to load the selected template then suddenly it disappears and the windows show the dialogue box to Check online help, debug or close it.
Next, visual studio reboots to the start page.
This only happens when I select any .Net Core or .Net Standard project templates.
Much appreciate your help in advance.
I had the exact same issue. It turned out that when a .Net core or .Net standard project template is selected, it tries to restore the packages from NuGet and somehow it was unable to do that or clear the NuGet’s local cache.
Here are the steps to fix it:
Download NuGet
https://dist.nuget.org/win-x86-commandline/latest/nuget.exe
Open the command prompt as “Administrator” – this is important other
cache may not get cleared due to permission issues.
Navigate to the folder where the NuGet is downloaded
Run the following command to clear the cache
nuget locals all -clear
Open Visual Studio 2017
Create a new ASP.Net core project with default templates
Hope this helps!
I am now using the Visual Studio 2013, where I want to create a web deployment installer for project like I am doing in Visual Studio 2008.
But I am not getting any option inside Setup and Deployment. Can anybody please guide me how to create the installer package for web application? I have publish folder ready with me. Can I create any installer from VS2008 using this Publish folder?
Visual Studio no longer includes a setup installer out of the box. This was removed in VS2012; the guidance instead is to use a 3rd party option like WiX or InstallShield.
Another option, if you don't need to use an MSI based installer, is to use Web Deploy. A web project in VS can create a deployment package, which can then be published to any number of websites at any time. It can also be customized by configuring parameters and setting their values at deploy time (link). Web Deploy packages can support deploying your web content, IIS settings, and database.
VS2013 will support it again. It will be released in the next update patch of the VS2013.
http://visualstudiomagazine.com/articles/2014/04/18/microsoft-reinstalls-visual-studio-installer.aspx
So I have a web application in visual studio. I can right click on the project and click Deploy which will send the files live to the SharePoint server.
I accidentally reverted one of the pages to an older version in Visual Studio and was wondering if it's possible to get the version running live on the SharePoint server as that is the latest version.
I cannot currently deploy as this will then run and old version of the page I accidental reverted.
Where would the files be stored and how could I find them? visual Studio is running on the SharePoint server.
Thank you very much!
Visual Studio does compile your *.aspx.cs files to the *.dll file of your Solution/Project.
If you want to get the code of your old *.aspx.cs file you can use Reflector or ILSpy to decompile your *.dll (actually deployed to your SharePoint) and find the old code by namespace.
According to Microsoft the side-by-side installation of Visual Studio 2010 and 2012 is supported (http://msdn.microsoft.com/en-us/library/ms246609.aspx).
I already had VS 2010 installed on my system (Windows 7 box) along with the Windows Azure Tools 1.5. I used this configuration to create a cloud project that is hosted on Azure. A few days ago I decided to also put VS 2012 on my system but to do it in a side-by-side manner rather than upgrading (or uninstalling) the VS 2010. The reason why I did not want to uninstall VS 2010 was that I already had some add-ons configured for it for script and css minification and aggregation. I heard that VS 2012 has this functionality built-in but I did not want to touch the dozens of scripts that I had already created using the older method. So I wanted to keep my VS 2010 environment in a pristine, working state in case there was an emergency and I had to publish a patch for my already hosted application. I would use VS 2012 for all the new projects going forward.
However, after I put VS 2012 on my box it also brought down 1.8 version of Azure SDK. As a result, I can no longer successfully build my VS 2010 solution. I have one worker role and one web role in that solution. If I build each one of them individually the builds succeed. But if I then try to build the entire solution or package it, it fails with no message in the log whatsoever. It just shows "Build Failed" in the VS status bar.
Since I was not getting any error in the status bar, I decided to create a "Hello World" application from scratch with only one web role using Windows Azure Cloud project template in VS 2010 hoping to get a better error message. Indeed, when I try to build the entire solution I get an error:
Error 102 WAT080 : Failed to locate the Windows Azure SDK. Please make sure the Windows Azure SDK v1.5 is installed. C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v10.0\Windows Azure Tools\1.5\Microsoft.WindowsAzure.targets
Clearly the installation of VS 2012 and Azure SDK 1.8 corrupted the older version. Ideally I would like to keep VS 2010 + Azure SDK 1.5 truly side-by-side with VS 2012 + Azure SDK 1.8. Is there a way to do this? If not, then how can I fix the error above? In other words, how can I fix VS 2010 to work with Azure SDK 1.8?
All you help is greatly appreciated.
Regards,
Archil
I solved this by going to Microsoft site and installing Windows Azure SDK for .NET - October 2012 (1.8).
http://www.microsoft.com/en-us/download/details.aspx?id=35448
Initially I was a bit afraid and people were saying that it would not work and they encouraged to do a manual one-by-one install. However, I decided to use the Web Platform Installed link from the above page:
http://go.microsoft.com/fwlink/?LinkId=254269
All in all, things went smoothly.
I am a new developer for Umbraco. I am having problem setting up my Visual Studio 2010 as a developer platform for umbraco 4.5.x with TFS and between remote teams.
My current setup is to open the whole umbraco site in Visual studio and tideup with TFS. Obeviusly this means that some of the files and folders gets locked up when commiting to Source control. Problem is this causes the problem when running umbraco as umbraco tried to write to certain files.
Any idea what type of typical setup would be like for VS 2010 and umbraco?
thanks,
Preyash
This should solve your problem =)
EDIT: Link updated
http://our.umbraco.org/wiki/codegarden-2009/open-space-minutes/working-in-visual-studio-when-developing-umbraco-solutions
I made a VS2010 umbraco project template, that configures the commands used to copy files to the umbraco folder on build, like described in the above link.
http://our.umbraco.org/projects/developer-tools/visual-studio-2010-project-template
Is it mandatory to use TFS as your version control?
We have used Mercurial and Visual svn server as version controls in our projects.
In this i feel Mercurial as more comfortable for Umbraco projects.