Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

API version mismatch #4

Closed
andrewdavey opened this issue Feb 18, 2015 · 7 comments
Closed

API version mismatch #4

andrewdavey opened this issue Feb 18, 2015 · 7 comments

Comments

@andrewdavey
Copy link

On loading my typescript project in Visual Studio 2013, I'm getting an Assertion Failed dialog box. I can click Ignore and continue to load the project. Is there something configured incorrectly on my system?

API version mismatch: managed version '0.4', script version '0.5'

   at TypeScriptLanguageService.CompilerServices.TypeScriptServicesFactoryProxy.ReportError(String message)
   at TypeScriptLanguageService.CompilerServices.TypeScriptServicesFactoryProxy.InitializeEngine()
   at TypeScriptLanguageService.CompilerServices.TypeScriptServicesFactoryProxy.InitializeJavaScriptEngineIfNecessary()
   at TypeScriptLanguageService.CompilerServices.TypeScriptServicesFactoryProxy.GetFactoryObject(Int32& fileVersion)
   at TypeScriptLanguageService.CompilerServices.TypeScriptGlobalServicesAccessor.CreateProxy(Int32& servicesFileVersion)
   at TypeScriptLanguageService.CompilerServices.TypeScriptServicesAccessorBase.get_Proxy()
   at TypeScriptLanguageService.CompilerServices.TypeScriptGlobalServicesProxy.GetDefaultCompilationSettings()
   at TypeScriptLanguageService.ScriptContext.DefaultCompilationSettingsProvider.GetDefaultCompilationSettings(ITypeScriptGlobalServicesProxy typescriptGlobalServicesProxy)
   at TypeScriptLanguageService.ScriptContext.ScriptContextComputeTask.Run(ITypeScriptGlobalServicesProxy services)
   at TypeScriptLanguageService.CompilerServices.TypeScriptGlobalServicesTask.Run()
   at TypeScriptLanguageService.Threading.BackgroundThreadQueue.<>c__DisplayClass8.<ExecuteOneTask>b__4()
   at GuardMethodClass.GuardMethod(Func`1 , Func`2 , Func`2 )
   at TypeScriptLanguageService.VsErrorReport.ExceptionFilter.Guard(Func`1 target, Func`2 filter, Func`2 handler)
   at TypeScriptLanguageService.Threading.BackgroundThreadQueue.ExecuteOneTask(BackgroundTask task)
   at TypeScriptLanguageService.Threading.BackgroundThreadQueue.ExecuteTasks()
   at TypeScriptLanguageService.Threading.BackgroundThreadQueue.Loop()
   at System.Threading.Tasks.Task.InnerInvoke()
   at System.Threading.Tasks.Task.Execute()
   at System.Threading.Tasks.Task.ExecutionContextCallback(Object obj)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot)
   at System.Threading.Tasks.Task.ExecuteEntry(Boolean bPreventDoubleExecution)
   at System.Threading.Tasks.Task.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()
   at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()
@fdecampredon
Copy link
Owner

:/ the problem is that I started to work on that from master typescript and that there is no visual studio version that manage it, I would prefer to avoid a commit that will make me diverge from typescript in other area than jsx support.

You have 2 solutions there:

  • wait for ts 1.5 release and the vs update that comes with it
  • a hackicsh solution would be to update typescriptServices.js manually and to search for the line :
ts.servicesVersion = "0.5";

And replace the 0.5 with 0.4, I'm pretty sure that the current version of jsx-typescript services does not differ from the 0.4 service api since I'm able to use it in my editor and that it's based on 0.4 api

@nathggns
Copy link

You could have a branch that has visual studio compatibility? Then update it to be the same as master when typescript 1.5 comes out?

Sent from my iPhone

On 18 Feb 2015, at 17:11, François de Campredon notifications@github.com wrote:

:/ the problem is that I started to work on that from master typescript and that there is not visual studio version, I would prefer to avoid a commit that will make me diverge from typescript in other area than jsx support.

You have 2 solutions there:

wait for ts 1.5 release and the vs update that comes with it
a hackicsh solution would be to update typescriptServices.js manually and to search for the line :
ts.servicesVersion = "0.5";
And replace the 0.5 with 0.4, I'm pretty sure that the current version of jsx-typescript services does not differ from the 0.4 service api since I'm able to use it in my editor and that it's based on 0.4 api


Reply to this email directly or view it on GitHub.

@fdecampredon
Copy link
Owner

@nathggns yeah that's a possibility a dummy branch just for vs support, but could you or @andrewdavey confirm changing the line I specified that everything works fine by just downgrading the string ?

@andrewdavey
Copy link
Author

Yes, changing the version number to 0.4 works. Thanks.

@nathggns
Copy link

I don't use visual studio or this project currently. Im just interested in it so I watch it. Sorry I can't help more.

Sent from my iPad

On 18 Feb 2015, at 17:29, François de Campredon notifications@github.com wrote:

@nathggns yeah that's a possibility a dummy branch just for vs support, but could you or @andrewdavey confirm changing the line I specified that everything works fine by just downgrading the string ?


Reply to this email directly or view it on GitHub.

@fdecampredon
Copy link
Owner

no problem @nathggns , thanks @andrewdavey, I'll branch and release a new beta version that just downgrade this string

@fdecampredon
Copy link
Owner

Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants