I originally had Visual Studio 2015 Enterprise CTP and it's expired. I uninstalled it and installed Visual Studio 2015 RC Community. However, it still says "This license has expired" (and any attempt to sign in fails as I don't have MSDN subscription). I uninstalled Visual Studio 2015 RC Community with /force command-line switch, removed all VSCommon, VisualStudio and Visual Studio disk folders and registry entries, and also Licenses registry subbranches requested by Visual Studio during startup (accordingly sysinternal's Process Monitor), and then reinstalled Visual Studio 2015 RC Community. I also run devenv.exe /resetuserdata (normally and under Administrator) with no luck. I'm running Windows 7 x64 if this matters.
It keeps telling "This license has expired". "Check for an updated license" tries to sign me in with no luck. Signing in with my Live.com account doesn't work (again, only MSDN subscription would suffice there). How else can I make Visual Studio "forget" that I previously had Visual Studio 2015 Enterprise CTP?
Is reinstalling the OS the only solution?
Unlike possible duplicate, I focus here on exact errors which are happening.
Have you tried a simple repair? Control Panel - Programs and Features - Microsoft Visual Studio Enterprise 2015 - Change - Repair.
I had the same problem. Tried uninstall and didn't work. Before going to registry manipulations, tried this:
Close the IDE, go and create your Visual Studio Online free account.
(https://www.visualstudio.com/en-us/products/what-is-visual-studio-online-vs - hope the link works)
Open IDE, and click "Check for updated license".
Login with that account, and hopefully this will work, as with my VS -
"License downloaded successfully".
It turned out that IE8 was the problem. Once I updated to IE11, signing to Live.com finally worked. So, the core of the problem was IE version.
Related
Got a big problem with the Visual Studio 2017 Installer Projects Extension for Visual Studio 2017 Professional. I added a Visual Studio Installer Setup project to a solution and set it up the way it's basically supposed to be done (Primary Output in the Application Folder and an icon in the Desktop Folder is all that was needed). Then I right-clicked on the Setup project, clicked "Build" and then I get this:
Please wait while Windows configures Microsoft Visual Studio Professional 2013.
And then it stalls indefinitely. I have to close Visual Studio in Task Manager to stop everything. What's more, I'm Visual Studio Professional 2017, not 2013. I used to have Visual Studio 2013 Ultimate, but I uninstalled it. What could possibly be causing the confusion?
It appears that you have also got Visual Studio 2013 installed, and that there is as conflict between 2013 and 2017 because that message is a Windows Installer repair of VS 2013. Something is happening during your build that requires the VS 2013 installation to be repaired. The Windows Event Log (Application) will have an MsiInstaller log entry saying which component appears to be broken. If you post that information there may be a clue to the problem. If you (for example) have manually removed anything that may belong to the VS 2013 installed product then that would cause the same kind of problem.
You have this similar problem:
Rebuilding Visual Studio Installer project, launches Visual Studio 2013 seetup
Visual Studio 2015 msi build initiates another installation
When you say it stalls indefinitely, I would expect it to ask for the Visual Studio 2013 install image so that it can repair it. If you go to Programs&Features and manually repair VS 2013 it might fix the problem.
I also had Visual Studio 2013 installed as mentioned by #PhilDW.
Navigating to Event Viewer → Windows Logs → Application I found loads of warnings:
Detection of product '{9C593464-7F2F-37B3-89F8-7E894E3B09EA}', feature 'Visual_Studio_Professional_x86_enu', component '{E3FF99AA-78B9-4A06-8A74-869E9F65E1FE}' failed. The resource 'C:\WINDOWS\Microsoft.NET\Framework\URTInstallPath_GAC\' does not exist.
The key here being that the folder C:\WINDOWS\Microsoft.NET\Framework\URTInstallPath_GAC\ did not exist thanks to an answer in the first link provided by #PhilDW.
Created the missing final folder URTInstallPath_GAC in the path mentioned and the installers now build really fast whereas before they used to take forever (sometimes literally!).
I have Visual Studio 2013 which included "PreEmptive Dotfuscator and Analytics".
It's always worked fine for me until recently.
Suddenly it will not open from Visual Studio, icon or commandline.
Even when I manually open it, it does not show up in the task manager.
It simply does nothing.
There's nothing in the Event Viewer logs.
Visual Studio shows no error.
Basically, I can't even begin to find the problem.
I tried to find a download to attempt to reinstall it but all I've seen on the website for this version is that it's included in VS2013.
There's other sites in search results which claim to have the installer but none I trust.
Has anyone had this issue in the past?
It's Visual Studio 2013 Professional on Windows 8.1.
I'm not sure how to address this so I would greatly appreciate any possible input.
Thanks in advance!
You can try uninstalling, wiping the settings, and reinstalling. Dotfuscator Community Edition is uninstallable via the Windows control panel. Once uninstalled, delete %LOCALAPPDATA%\PreEmptive Solutions. You may be able to reinstall it as a component via the Visual Studio installer. If not, it is actually a standalone installer, so if you have a Visual Studio disc or .iso, it will be in \packages\Dotfuscator.
I have Visual studio 2012 Professional already installed on my machine. I installed Visual studio Ultimate. I am not seeing Intellitrace windows or in IntelliTrace options in Tools-->Options in VS 2013.
I know, IntelliTrace is not available with Professional version. Am I missing anything?
What you are doing here should be supported. There are a couple of things that you can do to trouble shoot the issue.
1) Double check that you are actually launching Visual Studio 2013. I know that this sounds silly, but different versions of Windows will set up file or project associations differently. So, though you have installed 2013, it is possible that your regular workflow is actually still launching 2012. Check the splash screen and/or the Help > About dialog.
2) Reset Visual Studio. It is possible that something got corrupted in your extensions cache during your installation that is preventing Visual Studio from recognizing IntelliTrace. This should be relatively simple:
Launch the "Developer Command Prompt For Visual Studio 2013"
cd to [Program files x86]\Microsoft Visual Studio 2013
Execute the command "devenv /updateconfiguration" followed by "devenv /setup"
The last step may take a number of minutes depending on your system configuration. After it is finished, relaunch Visual Studio to see if IntelliTrace is available.
I have a newly built Windows 8 VM with VS 2012 Premium running on it, when I try open any sln file I get the following modal pop up error
Visual Studio 2010 Shell
Invalid license data. Reinstall is required.
I can open the sln's if I open up VS and then do project open, this is really annoying, any ideas how I fix it?
*Note I have done a VS repair and it didn't solve it...and I never had any VS RC release on the machine, all new build with s/w downloaded from the MSDN
Cheers
I encountered the same exact error when I created a solution with a full version of Visual Studio 2012 Professional on one machine and then tried to open the solution file with a copy of Visual Studio 2012 Express on a different machine. I got the error when double-clicking the solution file, but not when loading the solution into an already opened instance.
I fixed the error by opening the solution file (.sln) with notepad and changing the line that says Visual Studio 2012 to say Visual Studio Express 2012 for Windows Desktop.
After that, I was able to double-click to open the solution file on the machine that has Express installed.
I'm using VS 2013. I fixed this by right clicking the .sln and setting the Open With parameter to visual studio 2013 and not VS version selector or VS 2010.
I have faced the same problem. When I set the system Date and Time to the current Date and Time, The Problem solved by itself.
It looks like the .sln extension is owned by "Visual Studio 2010 Shell" a minimal version of Visual Studio that ships with products like SQL Server and Office to provide support for add-in development without any other features. Since this is a minimal version, it's unable to load any project type that ships with Visual Studio Express, Professional or above.
The same may happen when you have Visual Studio Express installed next to a full version of Visual Studio.
This may happen when you install an older version of Office or SQL Server after having installed Visual Studio. The old installer will hijack the extension.
To repair this problem:
use the "Open With" option of Windows and select the "Visual Studio Version Selector" as your default action.
Or open the "Default Programs" option in Windows, look up the .sln extension and make sure it uses the "Visual Studio Version Selector" as default:
Or locate Visual Studio 2012 in the Programs and Features window of Windows and chose "Change", the Visual Studio installer will pop up, chose "Repair" to have it repair the file associations and any other problems that may arise by installing Visual Studio versions in reverse order (it may for example mess up the MsBuild directory as well).
Remember that when Visual Studio 2010 was released, it could not yet know what Visual Studio 2012 would change, as such, it's best to install versions of Visual Studio in the order they were released. This may sometimes prove difficult, as other products may install Visual Studio versions without you knowing.
I recently installed Visual Studio 2010 Premium at my work computer. I'm evaluating the installation of the VS2010 SP1 Beta to adjust many little problems that I've noted in using VS2010.
But I don't know if the SP1 Beta is rollbackable or if If'll have to reinstall all the VS2010 when the final SP1 will arrive to us.
Could anyone advise me about the opportunity to do this?
thanks a lot
rob
From Scott Hanselman's blog:
•If you install VS2010 SP1 beta, don't
uninstall it if you can avoid it.
Rather, wait for SP1 final which will
upgrade your beta cleanly and leave
you in the best state.
This is a copy from the readme file at http://go.microsoft.com/fwlink/?LinkId=207141 :
2.2. Uninstalling
2.2.1. On computers that have earlier versions of Visual Studio
2.2.1.1. Uninstalling Visual Studio 2010 SP1 Beta removes features in
Visual Studio Tools for Office and
Visual Studio Tools for SharePoint
Uninstalling Visual Studio 2010 SP1
Beta removes the Visual Studio Tools
for Office (VSTO) Design Time and some
features of Visual Studio Tools for
SharePoint. The Office and Sharepoint
features in Visual Studio 2010 SP1
Beta are major upgrades and have
different product guids than those in
the Visual Studio 2010 original
release. Therefore, when SP1 Beta is
removed, the features are removed, and
the Visual Studio 2010
original-release versions must be
reinstalled.
To resolve this issue:
In Windows Control Panel, click
Uninstall a program. In the list of
programs, right-click Microsoft Visual
Studio 2010 and then click
Uninstall/Change. In the Maintenance
Mode dialog box, click Next and then
click Add or Remove Features. Select
the following features. Microsoft
Office Developer Tools (x86) or (x64)
for Office development. Microsoft
SharePoint Developer Tools for
SharePoint development. Click Update.
2.2.1.2. Uninstalling Visual Studio 2010 SP1 Beta may not donwload all
required packages
When Visual Studio 2010 SP1 Beta is
uninstalled by using Add/Remove
Programs in the Control Panel, a
prompt for source may be displayed.
To avoid this, run setup.exe from the
original location, and uninstall by
using Setup Maintenence Mode.
To resolve this issue:
Navigate to the original installation
location for Visual Studio 2010 SP1
Beta . Run setup.exe. Select Remove.
Update
Regarding your comment below, yes, I installed VS 2010 SP1 Beta, here are the problems I got:
I couldn't install Visual Studio SDK - Fixed - I found there was newer version for VS2010SP1Beta that I didn't realize at first.
I could not install Phone Developer SDK - Fixed as unrelated - I contacted #ScottGU and they said this is test scenario, I downloaded again and it worked as a charm
Few issues about Resharper or so (can't remember exactly, but minor for sure) - Fixed - I just got a recent build of Resharper.
If this leads to the question "Should I install it?", I'd say, if you need any of the new features in it (see http://msdn.microsoft.com/en-us/library/gg442059.aspx for listing), then just install it. It's OK. If not, wait for RTM.
BTW,
If you want to discuss your specific SP1 issues instead of uninstall, no problem in that as well :)