I want to create an Asp.net Core project with Visual Studio 2017 Community but the Solutions explorer says that I have (0 projects).
I tried selecting an empty project, web application, web application (Model-View-Controller) but the Solution explorer still displays (0 projects).
When I go-to Debug I see the "Attach to Process" option. There is no option to start of course since I have no projects.
What could be the issue?
Have you installed everything correctly? To verify this, open a normal cmd and just type 'dotnet'
Only if the command runs, printing out information about how to use dotnet, you're good to go.
Have you installed the correct .NET SDK? What version of it? Make sure the version is compatible with the version of visual studio you have installed.
Follow this link for step by step setup instructions:
https://www.c-sharpcorner.com/article/getting-started-with-net-core-on-visual-studio-2017/
This could be the same problem, but I had the same issue during College once but this time I had the support for the web components, so I went back to the installation and repaired it. It downloaded the missing files and it worked again and it took a while.
Let me know if that works or not.
So, I feel like I don't have all of the Visual Studio components that I need on my personal computer. For example, when I create a new ASP.NET application on the school computer, it generates files with it (program.cs, startup.cs, and appsettings.json), but those don't exist when I try to create a project on my laptop.
I just had a huge issue trying to get Scaffold-DbContext to work (and after about an hour of digging, finally found the commands to run in Package Manager Console that would allow that much to work). I'm sure there are other things I'm completely missing and don't realize it yet.
What do I need to do to get these files to be generated when I create a new project? Are there other things that I haven't installed for Visual Studio yet that I probably should? I'm really at a complete loss here.
Bring up Visual Studio. Click on Tools. Click Get Tools and Features...
Compare whats installed with what you have at school.
These three will do most of what your looking for:
.Net desktop development
ASP.NET and web development
Data storage and processing
Also look at the versions Help About Microsoft Visual Studio
While I was trying to Update my Project I was making - I got an error for the first time I've seen:
'An error occurred while signing: SignTool.exe not found.'
I've never seen this before, So I looked up that SignTool.exe is what signs my project for ClickOnce Deployment.
I also read that is it a part of Windows SDK - but when I looked to find where SignTool.exe is - I saw it right there!
C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bin
I saw no problem, and I've always published my Project all the time - I'm on Version 68. But this is the first time I've seen this - I didn't touch any options that would do this.
Any help?
ClickOnce Publishing Tools are not installed as part of the Typical Installation Options. So you have to install it in advanced mode.
This dialog can be found in Windows 7 by going to Control Panel > Uninstall a program, right-clicking on Microsoft Visual Studio Professional 2015 and selecting Change. A Visual Studio dialog will open up. Select Modify from the set of buttons at the bottom and the above dialog will appear.
Please Click Once application --> Properties --> Signing -> Unchecked the Sign the ClickOnce manifests.
Problem will be solved.
Note: Be aware that this solution removes security from your project. Seek assitance from a more learned colleague before doing so.
SignTool is moved to another location in the last SDK: C:\Program Files (x86)\Windows Kits\8.1\bin\x86
Need to install ClickOnce Publishing Tools during Visual Studio 2015 setup.
You can re-run the Installation from the Programs and Features section; find Visual Studio in the list and click Change.
You can fix this by clicking on installation application of VS. Then click Modify > Mark ClickOnce App and then upgrade your VS. Also i think #Alex Erygin is right. It is a bad solution to Click Once application --> Properties --> Signing -> Uncheck Sign the ClickOnce manifests. This is not a solution. It only circumambulated the problem.
This is a simple fix. Open the project you are getting this error on. Click "Project" at the top. Then click " Properties" ( Will be the name of the opened project) then click "Security" then uncheck "Enable ClickOnce security settings."
That should fix everything.
Click "Project" at the top. Then click " Properties" -> Signing -> Unchecked [Sign the ClickOnce manifests] is now working
Now try to publish the ClickOnce application. If you still find the same issue, please check if you installed the Microsoft .NET Framework 4.5 Developer Preview on the system. The Microsoft .NET Framework 4.5 Developer Preview is a prerelease version of the .NET Framework, and should not be used in production scenarios. It is an in-place update to the .NET Framework 4. You would need to uninstall this prerelease product from ARP.
https://blogs.msdn.microsoft.com/vsnetsetup/2013/11/18/an-error-occurred-while-signing-signtool-exe-not-found/
Lastly you might want to install the customer preview instead of being on the developer preview
None of the answers above talk about disabling ClickOnce. In my situation, I never used ClickOnce for my applications but after I upgraded to VS 2015 it was suddenly enabled and I got the 'SignTool.exe not found' error when I tried to compile.
To disable you go into the properties of your Project (right click) and choose Security | Uncheck Enable ClickOnce security settings.
You can leave the manifest checked in the Signing tab because it has nothing to sign if it's been disabled.
I've confirmed that unchecking the security resolved the compile error on my projects.
I needed Signing hence couldn't un-check as suggested.
Then goto Control Panel -> Programs and Features -> Microsoft Visual Studio 2015 Click Change then the installer will load and you need to click Modify to add ClickOnce Publishing Tools feature.
I did have similar problem. For some reason under
project properties -> Signing -> Sign ClickOnce manifests was enabled.
I unchecked it and the problem went away.
Reinstalling SDK did not help me but installing SDK+.NET 3.5 did from link below:
https://www.microsoft.com/en-us/download/details.aspx?id=3138
Windows 10 users can find signtool.exe in C:\Program Files (x86)\Windows Kits\10\bin\10.0.18362.0\x64 folder (10.0.18362.0 in my case, or other version).
But first, make sure you've installed Windows 10 SDK
Then, check Windows SDK Signing Tools for Desktop Apps is installed by going to Control Panel > Programs > Programs and Features, choose Windows Software Development Kit - Windows 10.0.18362.1 (in my case, you version may be different), right-click, choose Change, choose options Change then click Next.
I had the same issue/error message just after upgrading Visual Studio Pro 2019 V16.6.0. Solution was to make sure that the signing certificate is valid as mine had expired by a day.
Look in properties and signing to either enter a valid or temporary certificate. To keep the file name the same as before then un-click the security as mentioned above and then delete the key file linked to the programme.
Create a new key file and then add back the security.
Solution Explorer
Your app Right Clik
Propatis
Security
Unchek (Enable ClickOnce Security Settings)
Thats Solve..... __:)
https://i.stack.imgur.com/62nKZ.png See
[enter image description here]
After upgrading build tools in DevOps build agent to visual studio 2019, we started getting the below error for 64-bit build step of a WPF application.
C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(3975,5): error MSB3482: An error occurred while signing: SignTool.exe was not found at path
I tried all the above answers except the ones to disable signing or signing security and nothing helped.
Disabled the default MSBUILD step
Added a cmd prompt step
The path is
"C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Current\Bin\MsBuild.exe"
Note: Removed amd64 from the path above.
This is still a workaround. I hope Microsoft will fix it in the following release.
For VS 2019 or later (Windows 11)
Option 1 (Recommended) -
ClickOnce Publishing Tools are not installed basic Installation. Therefore you will have to manually check and install.
Go to Visual Studio Installer
Then Click modify
Finally, select Individual components tab, search for ClickOnce Publishing and install
Restart the computer.
Option 2 (Not recommended) -
Click Once application --> Properties --> Signing -> Uncheck Sign the ClickOnce manifests. This is not a solution. A workaround.
Option 3 -
Install Windows 10 SDK. Check Control Panel > Programs > Programs and Features > Windows Software Development Kit
I'm trying to create a Setup Project. I have opened my solution and the main project in my solution as per these instructions:
http://msdn.microsoft.com/en-us/library/19x10e5c.aspx
I clicked File>Add>Add Project and it brought up the add new project window. But then the tut says to "in the Project Types pane, open the Other Project Types node, open Setup and Deployment Projects."
The problem is, I don't have a Project Types pane. Nor do I have anything saying Other Project Types or Setup and Deployment Projects. I have a pane with Recent Templates, Installed Templates and Online Templates in it, but that has no Other Project Types in it or anything of use. So I went to Online Templates. This looked promising, it had an other category. But there is nothing setup related in sight. So I used the search tool for Setup. Nothing. The tut says its for visual studio 2010. Do I need the non-express version? How can I get this wizard?
Thankyou,
YoshieMaster
The express version does not come with all the whiz bangs of the full development suite, just the tools to develop apps, checkout the version comparisons Here
As as side, there's this solution on CodePlex, you could take that for a spin
Every time I use Setup & Deployment to create a new Web Setup, and run it (after edit all the nice things in the properties), the output is always a copy of the Web Site project...
How can I output a PreCompile version of the WebSite project?
What I did was, publish the Web Site (so I get the precompiled version), add this new precompiled web site as an existing Web site to my solution and add it to the content output of the Setup...
well, the idea was good but I get an error saying:
"This application is already precompiled."
alt text http://www.balexandre.com/temp/stackoverflow_precompiledquestion.png
:-(
Bottom line is that I just want a Setup file that gives me the precompiled version of my Web project, how can I accomplish this?
I see you tried the standard Web Setup project from VS.
Scott Gu's blog post takes you to this page:
Visual Studio 2008 Web Deployment Projects
which is a plugin for Visual Studio that activates an additional "right click" option to any Web Site project to add such a deployment project. You can see here what I created.... And the output is a pre-compiled web application. Now, if you add a regular Web Setup project to your solution, and point it to the previously created Web Deploy project as its content, ... I got a valid build, no errors and an MSI file was created...with dlls inside it.
http://img222.imageshack.us/img222/6177/71881923mj9.jpg
I hope this helps you.
I was searching for this solution from google for long days. What i did is i precompiled my website to one folder and added that folder as a new website to my
solution(While adding it will give a warning message that it was already precompiled content. No probs). Now add this project output to the my setup project and one more important thing is in my web deployment project i just disabled Building of my precompiled
website.
I just got my thinks working. If you want you can try that.
Regards,
Rousseau.A
you may be having "PrecompiledApp.config" file in the root of your web application (please check in solution explorer).
I faced this issue and removed "PrecompiledApp.config" from solution explorer and solved the issue.