VS2015 compatibility in Elements 2363?


(Richard E Walker) #1

VS2015 (14.0.25420.01 Update 3) Elements 10.0.0.2363: Attempt to load oxygene (java) project results in error message (details below). The project loads fine in VS2015 with Elements .2331

I see that the new Elements may have broken backward compatibility with VS 15.61 and require VS 15.8 (https://talk.remobjects.com/t/elements-2363-requires-vs-15-8/18467)

Will the latest Elements 2363 work with VS2015?

For example, the project shown: Did System.arraycopy change from elements 9 to 10?

ActivityLog.xml entry:

  <entry>
    <record>255</record>
    <time>2019/01/25 15:12:37.554</time>
    <type>Error</type>
    <source>VisualStudio</source>
    <description>SetSite failed for package [ExtensionsPackage]Source: &apos;Microsoft.VisualStudio.Shell.14.0&apos; Description: Due to high risk of deadlock you cannot call GetService from a background thread in an AsyncPackage derived class. You should instead call GetServiceAsync (without calling Result or Wait on the resultant Task object) or switch to the UI thread with the JoinableTaskFactory.SwitchToMainThreadAsync method before calling GetService.&#x000D;&#x000A;System.InvalidOperationException: Due to high risk of deadlock you cannot call GetService from a background thread in an AsyncPackage derived class. You should instead call GetServiceAsync (without calling Result or Wait on the resultant Task object) or switch to the UI thread with the JoinableTaskFactory.SwitchToMainThreadAsync method before calling GetService.&#x000D;&#x000A;   at Microsoft.VisualStudio.Shell.AsyncPackage.GetService(Type serviceType)&#x000D;&#x000A;   at Microsoft.VisualStudio.Shell.Package.Initialize()&#x000D;&#x000A;   at RemObjects.Oxygene.VisualStudio.ExtensionsPackage.&lt;InitializeAsync&gt;d__0.MoveNext()&#x000D;&#x000A;--- End of stack trace from previous location where exception was thrown ---&#x000D;&#x000A;   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)&#x000D;&#x000A;   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)&#x000D;&#x000A;   at Microsoft.VisualStudio.Shell.AsyncPackage.&lt;&gt;c__DisplayClass16_0.&lt;&lt;Microsoft-VisualStudio-Shell-Interop-IAsyncLoadablePackageInitialize-Initialize&gt;b__1&gt;d.MoveNext()&#x000D;&#x000A;--- End of stack trace from previous location where exception was thrown ---&#x000D;&#x000A;   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()&#x000D;&#x000A;   at Microsoft.VisualStudio.Services.VsTask.RethrowException(AggregateException e)&#x000D;&#x000A;   at Microsoft.VisualStudio.Services.VsTask.InternalGetResult(Boolean ignoreUIThreadCheck)&#x000D;&#x000A;   at Microsoft.VisualStudio.Services.VsTask.GetResult()</description>
    <guid>{8323D7DB-08A7-47D7-BF49-593A1FEF0FA9}</guid>
    <hr>80131509</hr>
    <errorinfo></errorinfo>
  </entry>
  <entry>
    <record>256</record>
    <time>2019/01/25 15:12:37.555</time>
    <type>Error</type>
    <source>VisualStudio</source>
    <description>End package load [ExtensionsPackage]</description>
    <guid>{8323D7DB-08A7-47D7-BF49-593A1FEF0FA9}</guid>
    <hr>80131509</hr>
    <errorinfo></errorinfo>
  </entry>

(Patrick Lanz) #2

The same error appears when loading a Silverlight solution… but I can still work on VS2015


(marc hoffman) #3

.2363 will work with Visual Studio 2015, 2017 and 2019 (Experimental). The only issue should be that for VS2017, you need to have the very latest update. Is that a problem? If so, why?

fwiw, .2365, due later today, should alleviate this requirement, but in general, it’s a but idea to stay up to date, and eventually we may purposely require the latest update patch level for VS. So if that’s a concern, I’d like to understand what the issues are that would make this problematic.

thanx,
marc


(Richard E Walker) #4

ASAIK I have the latest update to VS2015 and get the error I reported with .2363


(Richard E Walker) #5

Is the support for VS 2017 such that you can now recommend moving from VS 2015 to 2017? Previously I’d seen VS 2015 recommended…


(marc hoffman) #6

VS15.8 is Visual Studio 2017, not Visual Studio 2015 (thank Microsoft for the super smart naming). Visual Studio 2015 is VS14.x


(Richard E Walker) #7

?? I know that… I wrote that I have VS2015 (14.0.25420.01 Update 3) and I think this is the latest update for VS 2015 (v14)


(marc hoffman) #8

Ah sorry, i got confused because you also mentioned “I see that the new Elements may have broken backward compatibility with VS 15.61 and require VS 15.8”.

I’m not aware of ay incompatibilities with any version of VS2015, and this is the first report I see on this. I’ll have someone investigate.