I have been trying to deploy a web application is a .Net Framework
When I right-click on the project Solution, PUBLISH is nowhere to be found I tried Visual Studio 2017 and re-installed, checked and updated the workloads.
I check the checkbox: One-click publishing.
I gave up, I uninstalled it and installed Visual Studio 2019 same thing PUBLISH is not appearing anywhere.
I reset settings on import-export. I look everywhere on the NuGet package manager.
I am out of ideas.
Any hint would be appreciated. I will keep on digging. If ever I find a solution I will create a video because I spent several hours and my client is waiting for this application to be deployed on Godaddy Plesk. It is the first time I do this, I usually install scripts on LAMP Cpanel really easy.
This has been a nightmare for me, everywhere I see seems easy, right-click, click on Publish and create a profile or do Ftp or system files, azure.
But I can not get that blip Button PUBLISH.
Sorry, I am ranting.
You don't right click the solution itself to publish, you right click the web layer of your project and you would see the publish button
here
Ok I do not know if all the re-install and all did something but #fatihyildizhan suggested to click on the web app logo below the solution and it did the trick!
Related
I've been using VS for a while and have always pushed my code to github from within VS. I've just started a new project and want to do the same thing but in the Team Explorer github no longer appears. The options are either Team Services or Publish to a remote repository created outside of VS (which I understand in theory could be github but usually there is a github option within Team Explorer).
I've just created a new project called Test and github doesn't appear in this project either.
Anyone encountered this problem? And where can I check to see if the github extension is still installed?
Cheers,
Jerome
I noticed the same thing so I checked my Extensions and Updates and it looked like the Github extension uninstalled itself.
Searching the "online" pane for "github" allowed me to reinstall and now it's working again. Hope this helps.
You can access your Extensions and Updates by clicking on the Tools menu and it's about 3/4 of the way down the menu.
Earlier this year I successfully deployed a MVC app to Azure from Visual Studio.
Now I'm trying to do the same thing again, but now I am told my azure account "has no subscription".
However I am 100% positive I do have a subscription associated with my email. My old MVC app still runs and I can see my Pay-as-you-go is properly charged.
What I Have tried to fix it
Emptied my browser caches, history, cookies etc.
Removed my account from Visual Studio, restarted, and added them again.
Formatted my computer and reinstalled everything (not really because of this problem, but the timing was perfect).
Updated the Azure SDK to the newest 2.9.5.
I did the following things above based on advice from these pages:
Visual Studio not finding my Azure subscriptions
Unable to publish to Azure with VS2015
No subscription found in windows azure account
But alas, no luck.
The only thing that comes to thought is I tried to add an Azure Pass to my account, but without luck. But I can't see how that should change anything...
So my question is: How do I make Visual Studio recognize my current Pay-as-you-go subscription, so I can publish my services, apps, etc. from Visual Studio directly?
Or at least: What has gone wrong? Whom can I contact to get help with this?
As always, thank you for your time and patience, and please write a comment if you need further information.
You may try to connect first via the server explorer (ctrl+alt+s). (The server explorer has an azure root node, if the azure sdk installed)
If you have connected, the publish wizard won't ask (usually) for sign in again.
In my case, the solution was as follows:
Open Server Explorer in Visual Studio, right-click on Azure and select "Manage and filter subscriptions":
Screenshot of Manage Subscriptions Dialog
Click the Certificates tab, click Import, then click Download subscription file. This will take you to the azure portal page where you can download a .publishsettings file for your subscription. After downloading that file, click the Browse button in the Import dialog shown above and select that file.
I had the same issue. To solve it I opened the server explorer (ctrl+alt+s) and refreshed the Azure connection. It still said 0 subscriptions, but in the publishing options I could connect without any issue.
One of the web application projects in my visual studio solution has a blue exclamation mark icon on it and the tool tip shows The Web project <Project.Name.Here> has IIS configuration warnings
I can't see anything in the project Properties pages, or in the web.config file. It started yesterday, and I assumed restrating VS and reloading the project may get rid of the warning, but it has not.
What is this and how do I go about resolving this issue?
Google has not been helpful this morning!
Try right clicking the solution in the Solution Explorer, the option Resolve Errors should be available.
Selecting this should show you the message behind the icon you're seeing on the project. For me, this was:
ASP.NET 4.0 has not been registered on the Web server. You need to manually configure your Web server for ASP.NET 4.0 in order for your site to run correctly.
If this is the message you're receiving, this MS blog post may help you fix it.
Update
Note that once you've selected this option, the IDE assumes you've resolved the errors and removes the icon and menu option (!). So make sure you read it or restart VS to see it again.
I just started working in Visual Studio 2012 in a project group. We are using team foundation server to share our code. I have a couple of problems here I was hoping someone could help me solve them.
I have succesfully connected to our TFS-server and checked out the project, but for some reason when I check my solution explorer it says "0 solutions". I dont know if this is a problem but I feel like it has something to do with my other problems.
I can't, for some reason, press the play button to start debug, also in the menu the debug option is greyed out, 5 obv doesent work either. And in the "project" tab I dont have the option to set my project as startup project wich would make it so that I can debug it.
Check your Source Control Explorer. There you can navigate the code in TFS. Make sure there are files checked in to this location. If not, you will first have to add your project to TFS.
If there are files in TFS, map the files to a location on your harddrive. Then open the solution file by double clicking it in your Solution Explorer.
The MSDN has a nice walktrough: Set Up Team Foundation Server for Version Control
It turns out the local path has to be in the visual studidio\projects folder... re-mapped it and works as intended. No need to answer this anymore, thanks for your suggestions though :)
Im using VS express web developer, and attempting to create a new MVC project. The problem is, VS hangs when adding EntityFramework to the project. Its attempting to add EntityFramework 4.1.10331.0 to an MVC 3 project. Any ideas what might be going on?
It has been a while since you asked the question, but I recently stumbled across a similar issue except with MVC4 adding EntityFramework.5.0.0 in Visual Studio 2012 Ultimate.
The issue was that I was trying to create the project in a network folder (I run Windows 7 in a VM on top of OSX).
The problem appears to be that the network folder is not considered a Trusted Location. I had to go into Control Panel -> Internet Options, click "Security" tab, Click "Local Intranet" zone, then click Sites button.
In the "Local intranet" dialog which pops up, I un-checked "Automatically detect intranet network" and checked "Include all network paths (UNCs)"
Now I guess Visual Studio and/or nuGet see the network folder as a trusted location, and EntityFramework.5.0.0 is installed along with everything else a new MVC 4 project requires.
Credit goes to my colleague who referred me to this SuperUser post.
Bit of an old question, but it's still an issue today so this might help someone looking for a solution.
I don't have enough rep to comment on Chris Cameron's answer, so apologies for submitting it as a new answer - all credit should go to Chris. I found that to get it working I also needed to check "Include all local (intranet) sites not listed in other zones." Chris' solution then worked like a charm.