Since I updated Visual Studio Professional 2019 to latest version (16.3.4), I'm not able to publish my .NET Core console app to a folder anymore (I'm not using online services).
I used to right click on my executable project, click on "Publish" menu item, configure my publish profile in a dedicated window and then, of course, publish. This configuration was saved in a XML file in <myProjectFolder>\Properties\PublishProfiles\.
Now all I can see when I click on "Publish" menu item is the following empty page, from which I can do nothing, neither configure a publish profile nor actually publish.
Is there a way to fix this?
Related
Following instructions in this link to deploy with Clickonce:
https://learn.microsoft.com/en-us/visualstudio/deployment/quickstart-deploy-using-clickonce-folder?view=vs-2019
I right click in the project and select Publish, and the Publish wizard opens, with the "Target" tab selected as expected, and I select "Folder" option. Then, when I click the "Next" button, it does not appear the "Specific tab", but it goes directly to "Publish location" tab. The problem with this is that I cannot select "Clickonce" anywhere because I do not see the "Specific target" tab, so there is no "Install location", "Settings", "Sign manifests" or "Configuration" tabs.
This is the expected tab that not appears:
And this is the screen I see (sorry, it is in Spanish):
It is a .NET Framework 4.8 project.
Why is Clickonce missing? What can I do to get the right screen in the wizard so I can use Clickonce?
Thank you
UPDATE: I have tried to update to .NET 5, and then magically ClickOnce appears in the Publish wizard. So, how can I use ClickOnce with net48 in a SDK scheme project? Any help?
.Net Framework ClicOnce is not compatible with the SDK style projects, here the link discussion. So the correct answer here would be: is not possible.
What you could do is either downgrade your csproj style to old version or update your project to a .net core 5 or use cli msbuild to deploy.
The "expected tab" is the update content for .NET Core & .NET 5. As you said, when you update the target framework to .NET 5, the tab will be shown.
If you are developing with .NET Framework 4.8, you still can right-click the project and click Publish. Because it will be published via ClickOnce bu default.
Or follow the steps Project => Properties => Publish.
How do I enable debugging from VS2019 for my .NET app running in an Azure App Service? The portal only supports 2015 and 2017.
You can just connect from Visual Studio 2019 and it should all work without changing the portal settings.
Open Visual Studio and your project
Open Cloud Explorer View -> Cloud Explorer or ctrl+\, ctrl+x
Find your App Service node in Cloud Explorer and select it
Choose Attach Debugger from the context menu or the actions pane
The VS 2019 option doesn't display in the "Classic" Application settings screen, you will need to use the new Configuration menu, then choose the "General Settings" tab when the blade opens.
Have you downloaded and installed the VS 2019 Remote Tools?
https://visualstudio.microsoft.com/downloads/?q=remote+tools#remote-tools-for-visual-studio-2019 (see the bottom of the page)
I had the same problem. I closed VS 2019 and installed the Remote Tools. When I relaunched, I went to Cloud Explorer and i now have the menu items I'm expecting.
You can also set the remote debugging version to "VS2019" through https://resources.azure.com.
You'll need to find the Web App e.g. from under Subscription name / resourceGroups / RG name / providers / Microsoft.Web / sites.
Then open config / web.
Switch from Read Only to Read/Write at the top if you didn't.
Click Edit.
Modify the version and enable debugging by settings these under "properties":
"remoteDebuggingEnabled": true,
"remoteDebuggingVersion": "VS2019"
Click PUT.
Using Visual Studio Enterprise 2015 Update 3, I create a new project following these steps:
File -> New -> Project -> Templates/Visual C#/ Office/SharePoint/Apps
Choose App for Office (.NET Framework 4.5.2)
In Create app for Office window, Check Task pane and do Next
Check Excel, PowerPoint and Word and click Finish
After creating the solution, In Solution Explorer Window, Select the first project (manifest project) and look at the Properties Window.
If I click the Start Action drop down list, I can only see Chrome and Edge browsers (were installed before visual studio).
I have installed FireFox after visual studio and I'm not unable to add it to Start Action drop down list. I want to debug my Office App in FireFox as well.
How can I fix this issue?
An Office add-in running in desktop Office, which it is where it runs when you are debugging it with Visual Studio on a Windows machine, uses IE under the hood. (For more info, see what-browser-browser-engine-do-office-add-ins-use.) You can't change this. The Start Action setting has no effect. You are always using IE when you press F5. In particular, the Start Action of the manifest project is irrelevant because the manifest doesn't run or get loaded into a browser.
If you want to test the add-in in Office Online, you can sideload it, and when you run it, it will use whatever browser you used to open Office Online.
I am new to VS.
Went to Extensions and installed JSLint.NET, it is also enabled.
But I get no item under Tools to configure or use it?
JSLint.NET is configured on per project basis. Right click on your project and you should see a menu choice for JSLint.NET Project Settings.
You can see an example of this on the Visual Studio gallery page for the extension.
JSLint.NET Extension
I use VS 2010 and the deploy function and to get quick access to the functionality I showed Web One Click Publish toolbar. But the toolbar is only activated when I open Web.config files or when I open Properties of a web project. When I open C# code file that toolbar is disabled. I think the functionality should be enabled independently like for example functionality Build project.
Is it something wrong in my VS installation or configuration?
I've just found that it is disabled when code file being viewed (active) does not belong to Web project (but to other one instead that cannot be published).