I've just re-installed Visual c# 2010 express edition.
On my previous install, without any special edition i had a "Go to definition" button, whenever i right clicked a method.
As you can see, now it disappeared
I tinkered around the customization menus above, but they only provide commands in the main tool bar, and not on the right click.
I also tried installing 2 different versions of it, and on a computer where the old c# 2010 remains, the "go to definition" command is available when i right-click a method.
I tried exporting its settings, but no command "go to definition" appears on the new one.
How can I fix it, and how can I re-install exactly the same version of visual c# 2010 express that i have on the other computer? It's version is 10.0.30319.1 RTMRel
Solved it, it's unknown if it's a version problem (since I have a offline and a online one, with and without sp1), or simply application settings unrecognizable.
Follow these steps:
uninstall sp1 (using the installer)
uninstall vs2010
delete the installation folder, and the visual studio 2010 folder in the "my documents" (win7 version)
reboot and reinstall, it should be fine (i used offline installation for both vs2010 and sp1)
Related
I had a VS2015 solution with a C# and python project in it. Now I upgraded visual studio to "2017 community preview" version.
If I try to open the solution from Visual Studio by clicking on File/Open/Project... it pops up the following error message:
Unsupported. After that VS cannot open the python project in the solution (it sais "incompatible" next to the project file). It can open the C# projects.
But if I simply double-click on the *.sln file, VS automatically starts up and offers the following one-way upgrade: One-way upgrade. After doing the upgrade it can open the python project as well and everything works properly.
Even though after making the one-way upgrade the first type of opening (from VS) still does not work. Opening by clicking on the solution file still works.
Thanks for any help how I can resolve this issue.
Python tools for visual studio 2017 is only available for the preview version. It will be added soon to the non-preview version.
source: https://blogs.msdn.microsoft.com/pythonengineering/2017/03/07/python-support-in-vs2017/
OMG, I got the answer...
I had both VS 2017 community and VS 2017 community preview installed on my computer. (That is because obvously I installed the simple community version at first, and only installed the other when I realized it does not support python.) I did not either think that preview version will not overwrite the existing one but will make a new install.
So when I click on the sln file it opens up with the preview version of VS, but the shortcut in my start menu refers to the normal version... :S :D
I have Visual Studio 2013 Ultimate. Today when I opened it, it didn't load any of my solution's projects. Error message:
Unsupported
This version of Visual Studio is unable to open the following projects. The project types may not be installed or this version of Visual Studio may not support them.
For more information on enabling these project types or otherwise migrating your assets, please see the details in the "Migration Report" displayed after clicking OK.
- ETL_<Project name>, "<Project path></Project>.csproj"
Non-functional changes required
Visual Studio will automatically make non-functional changes to the following projects in order to enable them to open in Visual Studio 2013, Visual Studio 2012, and Visual Studio 2010 SP1. Project behavior will not be impacted.
- <Project name></Project>, "<Project path></Project>.sln"
These projects are of types Class Library and Console Application. If I try to create a new project, these types are listed, but when I create it I get message <Project path> cannot be opened because its project type (.csproj is not supported by this version of the application. To open it, please use a version that supports this type of project..
So, Visual Studio is telling me it doesn't support a project it just created?! GJ M$!!
Unfortunately I was unable to solve this. I ended up uninstalling VS Ultimate. Now I use VS Express for Desktop, and it works with my old projects.
My assumption is that something on Windows broke some part of VS. I should have tried to uninstall and reinstall it but didn't have the opportunity.
I have the same thing in a Hyper-V VM. After repair did not work, I deinstalled and reinstalled VS 2017. Same thing.
In the host I can still open the same project with VS, so it is not the project, but the VS install that has a problem.
It puts this in the migration log:
src\DTOWEB\project.json: Failed to migrate XProj project DTOWEB. Could not find project.json at C:\DTOWeb\DTOWEB7\src\DTOWEB\project.json.
I have a second VM that is x86 iso x64, and it can open the project without problems. So again, my conclusion is there is nothing wrong with the project.
I am running VS professional 2015 on my Windows 10 professional, and I needed to install the Crystal Reports runtime on my computer so I can build projects with CrystalDecisions.CrystalReports.Engine and CrystalDecisions.Shared, version 13.0.2000.0.
I also currently have Crystal Reports 2008, version 12.0.0.683 installed on my computer to create reports outside VS 2015.
On our company server, there was a .msi file and a .exe file. Like an idiot, I ran the .msi file without knowing:
To integrate "SAP Crystal Reports, developer version for Microsoft Visual Studio" into VS 2010 or 2012 (SP 7 and higher) or VS 2013 (SP 9 or higher) or VS 2015 RC (SP14) - VS 2015 (fully - SP 15), you must run the Install Executable. Running the MSI will not fully integrate Crystal Reports into VS. MSI files by definition are for runtime distribution only.
So after running the .msi file and realizing my mistake, I ran the "Uninstall" option from the .msi file and checked my GAC. The CrystalDecisions has been uninstalled from my "GAC_32" and "GAC_64" folders. However, the strange part is that in my "GAC_MSIL" folder, it has the CrystalDecisions version 12.0.2000.0.
GAC_MSIL folder - but no CrystalDecisions folders in GAC_32 or GAC_64
I checked my Control Panel -> Programs -> Programs and Features and nowhere can I find "SAP Crystal Reports runtime engine for .NET Framework (64-bit)" and "SAP Crystal Reports, version for Microsoft Visual Studio", so I figured the uninstall was successful.
When I try to run the .exe file this time, I get an error saying that it cannot run the installation due to the following error:
SAP Crystal Reports runtime installation error window
So I checked EventViewer -> Windows Logs -> Application, and the error log said it was an error at installation 1603 and "Product: SAP Crystal Reports, version for Microsoft Visual Studio -- You must already have Visual Studio 2010 or Visual Studio 2012 installed to proceed with this installation."
I talked with my boss and he said he doubts I need VS 2012 and it does not make sense to have both VS 2012 and 2015 on my computer. Unfortunately, I cannot build projects using CrystalDecisions v.13 like our production server, and building the project using the CrystalDecisions v.12 on my computer will cause the project to fail if I release it to production.
I checked other questions on StackOverflow, and I saw some solutions:
Install VS 2012 - not an option unless a last resort; we have VS 2015 only - unless if installing a "community" version of VS 2012 would do the trick.
Do a system restore - one person suggested because I ran the .msi file instead of the .exe, it messed up my assembly, so doing a system restore before I ran the .msi file could fix it and allow me to install CR runtime correctly, but again, my boss says he wouldn't recommend it
Try running the CR runtime setup from the SAP website with a newer version other than v.13 for my x64 bit machine that will integrate with VS 2015 without needing VS 2012 - then the newer version of my CR runtime when I build my projects will be different from the CR runtime on the production server and there will be conflicts when I release my project on the production server.
Alter/delete my assembly files because running the .msi file screwed up my assembly cache - Really risky; I don't know the first thing about assembly files and I could mess up my computer. And would deleting manually the "CrystalDecisions" folders from my "GAC_MSIL" folder even work if the GAC_32 and GAC_64 folders do not have "CrystalDecisions"?
None of these solutions are preferable, so does anyone have any other solutions I cannot see that work?
Thank you for your patience. I could just bash my head against the desk because I ran the .msi file instead of reading the directions carefully. I feel like an idiot...
To all those who are wondering, my boss and I fixed the issue and it was incredibly simple!
It turns out that we needed some Visual Studio 2012 tools installed on the computer before running the executable. We needed to install those SDK libraries in Visual Studio 2015 before running the installation of the "CRforVS_13_0_6.exe" file.
So I went to "Control Panel" -> "Programs and Features" -> selected Visual Studio Professional 2015 and clicked the "Change" button to go to the following menu:
Installing new Visual Studio 2015 SDK Features
We checked the "Windows 8.1 and Windows Phone 8.0/8.1 Tools" and made sure "Tools and Windows SDKs" was checked.
After updating, I restarted my computer and tried to run the Crystal Reports v13 for Visual Studio .exe again.
It worked!
So it looks like my boss's doubt was incorrect; you do need some VS 2012 components to run the CR v13 installation for Visual Studio!
Putting this here for future reference!
After a Visual Studio 2017 (RC) installation from scratch, I can't find a standard list of templates. I'm specifically interested in the Console Application (C#) template and the Windows Form (C#) template. I'm pretty sure I'm missing one of the Individual Components. I'm not sure which one is supposed to be installed and I don't want to install all of them.
Please see my list with components installed.
You need to install it by launching the installer.
Click the "Workload" tab* in the upper-left, then check top right ".NET-Desktop Development" and hit install. Note it may modify your installation size (bottom-right), and you can install other Workloads, but you must install ".NET-Desktop Development" at least.
*as seen in comments below, users were not able to achieve the equivalent using the "Individual Components" tab.
If you have installed .NET desktop development and still you can't see the templates, then VS is probably getting the templates from your custom templates folder and not installed.
To fix that, copy the installed templates folder to custom.
This is your "installed" folder
C:\Program Files (x86)\Microsoft Visual Studio
14.0\Common7\IDE\ProjectTemplates
This is your "custom" folder
C:\Users[your username]\Documents\Visual
Studio\2017\Templates\ProjectTemplates
Typically this happens when you are at the office and you are running VS as an administrator and visual studio is confused how to merge both of them and if you notice they don't have the same folder structure and folder names.. One is CSHARP and the other C#....
I didn't have the same problem when I installed VS 2017 community edition at home though. This happened when I installed visual studio 2017 "enterprise" edition.
I found the path and wrote it in the options
My personal experience was that I had installed the Team Foundation Server client for 2017 first (was using it as a Proof of Concept for our QA team, while I was still using VS2015), then followed it up with Installing Visual Studio 2017 later to begin development.
What I ended up with on my Start Menu was a Visual Studio 2017 and a Visual Studio 2017 (2). The Visual Studio 2017 (2) had all the templates I was missing. Following the steps found in the First answer to this question (which were clear and easy to follow) did not fix my issue. I had thought that launching the client would upgrade to the Development Client, but it did not. I renamed it to Visual Studio Professional, and now have everything I need. Not sure if this happens to anyone else, but it was what happened to me, so I hope this helps someone.
NOTE: this topic is about installation issues with MS project templates.
I came here via a search in Google, I was looking for a missing Template option in Visual Studio 2017 File menu: in VS-2015, it was Export to Template and I used it to add my own standard Project Items.
Meanwhile, I found an answer.. my issue was not related to default templates and it does not need install things. The option Export to Template has been moved to the VS-2017 Project menu !
I had to reinstall .NET desktop development (throught Workload tab), even button was showing: Modify
After that Visual C# selection appeared :)
(And now i can use Console APP Template)
In my case, I had all of the required features, but I had installed the Team Explorer version (accidentally used the wrong installer) before installing Professional.
When running the Team Explorer version, only the Blank Solution option was available.
The Team Explorer EXE was located in:
"C:\Program Files (x86)\Microsoft Visual Studio\2017\TeamExplorer\Common7\IDE\devenv.exe"
Once I launched the correct EXE, Visual Studio started working as expected.
The Professional EXE was located in:
"C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\devenv.exe"
My C++ templates were there all along, it was my C# ones that were missing.
Similar to CSharpie, after trying many modify/re-installs, oddly the following finally worked for me :
- run the installer, but un-select 'Desktop development with C++'.
- allow installer to complete
- run the installer again, and select 'Desktop development with C++'.
- allow installer to complete
In my case, I had all of the required features, but I had installed the Team Explorer version (accidentally used the wrong installer) before installing Professional.
When running the Team Explorer version, only the Blank Solution option was available.
The Team Explorer EXE was located in: "C:\Program Files (x86)\Microsoft Visual Studio\2017\TeamExplorer\Common7\IDE\devenv.exe"
Once I launched the correct EXE, Visual Studio started working as expected.
The Professional EXE was located in: "C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\devenv.exe"
This solved my issue, and the reason was I had enterprise edition previously installed and then uninstalled and installed the professional edition. Team Explorer was not modified later when I moved to professional from enterprise edition.
After finishing my C# application I had to make an installer. After seeing that the default installer projects are gone, i searched for a replacement.
I found the Visual Studio Installer Projects. I downloaded the file from here: https://visualstudiogallery.msdn.microsoft.com/9abe329c-9bba-44a1-be59-0fbf6151054d.
When i restarted Visual Studio, opened my project, clicked "add new project" and here is what I got:
Problem is that I cant find the setup project. I have tried repairing the install. I restarted Visual Studio several times.
My Question:
How can I find the installer project and why it's not working for me.
If I cant make it work, are there any alternatives ? (except InstallShield)
Additional info:
Visual Studio 2013 Community with update 4
Windows 8.1 64-bit
You could try Tools > Extensions and Updates and search for it:
Visual Studio setup projects no longer ship with Visual Studio
However, you can download them here.
Or use a third party library like WiX.
I had the same problem and it turns out that visual studio removed the support for installer projects in 2010.
but still you can download and install it in your version
VS2013
VS2015
VS2017