Install issue with TypeScript 1.3 on VS 2013 Premium

[danquirk]

Per https://visualstudiogallery.msdn.microsoft.com/955e0262-0858-40c9-ab5a-1acc680e9bfd?SRC=Home

Joel Mueller (SNL)
As soon as I install this package, VS 2013 Premium will not launch, giving me the message...

"A problem occurred when loading the Microsoft Visual Studio menu. To fix this problem, run 'devenv.exe /resetsettings' from the command prompt."

Doing so changes nothing. I get the same results whether installing on VS 2013 Update 3 or Update 4. Uninstalling the package allows VS to launch, but now I have no color coding, intellisense, or compile-on-save for *.ts files. Please help!

  <entry>
    <record>33</record>
    <time>2014/11/12 20:37:01.341</time>
    <type>Information</type>
    <source>VisualStudio</source>
    <description>Begin package load [Environment Package Window Management]</description>
    <guid>{5E56B3DB-7964-4588-8D49-D3523AB7BDB9}</guid>
  </entry>
  <entry>
    <record>34</record>
    <time>2014/11/12 20:37:01.357</time>
    <type>Error</type>
    <source>VisualStudio</source>
    <description>SetSite failed for package [Environment Package Window Management]</description>
    <guid>{5E56B3DB-7964-4588-8D49-D3523AB7BDB9}</guid>
    <hr>80131534</hr>
    <errorinfo>The type initializer for 'Microsoft.VisualStudio.Platform.WindowManagement.WindowManagerService' threw an exception.</errorinfo>
  </entry>

I rebooted, then ran "devenv.exe /ResetUserData". That seemed to clear things up, except for warning messages about how my TypeScript compiler was a newer version than my TypeScriptTools. So I did a Repair on this package, and I'm now back to Visual Studio not launching with the same message about how I should /resetsettings.

[basarat]

I've run into issues as well http://stackoverflow.com/questions/26898185/typescript-1-3-for-visual-studio-2013-missing-sdk-directory-tsc-exe/26899391#26899391. Investigating how to revert my system.

[jednano]

FWIW, I just installed VS 2013 Update 4 today, followed by TypeScript 1.3 for Visual Studio 2013. This was done on Windows 8.1. Everything appears to be functioning properly. I also removed a PATH reference from my system environment variables that was pointing to TS 1.0's tsc.exe.

[basarat]

@jedmao I suspect as much. I've uninstalled all TS and currently applying update 4. I'll let you know how it goes.

[basarat]

Update 4 + Powertools work. However there is the version inconsistency that I'll report in a separate issue

[johnnyreilly]

@basarat - do you think that installing Update 4 and then Powertools was the magic formula? Any other quirks left over?

I probably wont get a chance to upgrade until next week but when I do I guess I should make sure that I do both at the same time...

[jtmueller]

Let me know if there's any additional information I can supply on the original issue. Currently I have it to the point where the Error List is giving me this warning:

Warning: Your project file uses an older version of the TypeScript compiler and tools than supported by this version of Visual Studio. Your project may be using TypeScript language features that will result in errors when compiling with this version of the TypeScript tools. To remove this warning, remove the element from your project file.

This despite the fact that I already have removed that element from the project file. Compiling with the new language features seems to work, and manually setting TypeScriptToolsVersion to 1.1 seems to clear up the warning.

[mhegazy]

@jtmueller this means that the language service is older than you compiler. In 1.1 we only released the compiler and left the 1.0 language service. If 1.3 is installed successfully you should have matching language service and compiler and should not see this warning.

Did you try installing 1.3?

[billti]

I've posted a lengthy reply on the Stack Overflow thread explaining the versioning, folders, and warnings. Please see http://stackoverflow.com/questions/26898185/typescript-1-3-for-visual-studio-2013-missing-sdk-directory-tsc-exe/26915217#26915217 and see if that clears up this part of the question.

As to why you are getting the initialization failure - this seems unrelated to any TypeScript code paths. Searching around the only possible explanation I can find is as outlined at http://stackoverflow.com/questions/23634505/exception-has-been-thrown-by-a-target-of-invocation-in-visual-studio-2013 . Is it possible installing the update is appending to your PATH environment variable and exceeding the limit outlined? (Are you able to remove any unnecessary parts of the path and see if this resolves the issue)?

[paulvanbrenk]

@jtmueller Originally did you have Update 3 installed on VS premium and then applied TypeScript 1.3?

[JsonFreeman]

I was not able to hit this issue after installing Update 3 and then the TypeScript 1.3 package. Everything seemed to work just fine. @jtmueller, are those the steps you took, or did you do something different?

[basarat]

@johnnyreilly Update 4 + Power tools worked in the sense that I can work again. But not perfectly since my tools version is 1.1. That is the following is not valid for me:

If 1.3 is installed successfully you should have matching language service and compiler and should not see this warning.

Also @SteveFenton's experience seems to match : http://stackoverflow.com/a/26904493/390330

[JsonFreeman]

The tools version of 1.3 should actually be 1.1. That's expected. You should have the 1.3 language services with a tools version of 1.1, and the 1.1 folder should contain the 1.3 compiler. I realize this is confusing - sorry about that.

But you should not be getting the warning about the compiler version not matching the VS version. If you are seeing this after upgrading from 1.1 to 1.3, that is a bug.

[paulvanbrenk]

@basarat Which TypeScriptToolsVersion do you have in the project file?

[basarat]

But you should not be getting the warning about the compiler version not matching the VS version. If you are seeing this, that is a bug

Not seeing this warning. @paulvanbrenk its 1.1. @johnnyreilly Guess I am good to go.