StrataFrame Forum » StrataFrame Application Framework - V1 » Issues » Tried New VISX with VS 2013 and Win 10

Tried New VISX with VS 2013 and Win 10

Buffie — Tue, 13 Oct 2015 21:28:02 GMT

This is the error I get. Not sure how it will appear on your end. I just copied and pasted it.

I tried to install Dot net 4.5 and it says I already have it installed so I am not sure what else to check for?

TIA

[quote]9/9/2015 10:33:06 AM - Microsoft VSIX Installer

9/9/2015 10:33:06 AM - -------------------------------------------

9/9/2015 10:33:06 AM - Initializing Install...

9/9/2015 10:33:06 AM - Extension Details...

9/9/2015 10:33:06 AM - Identifier : 0d9a9c3f-5ef0-4d1f-b38e-7bc0918e291d

9/9/2015 10:33:06 AM - Name : MicroFour StrataFrame

9/9/2015 10:33:06 AM - Author : MicroFour, Inc.

9/9/2015 10:33:06 AM - Version : 1.7.7.1

9/9/2015 10:33:06 AM - Description : VSIntegration package for MicroFour StrataFrame V1

9/9/2015 10:33:06 AM - Locale : en-US

9/9/2015 10:33:06 AM - MoreInfoURL :

9/9/2015 10:33:06 AM - InstalledByMSI : False

9/9/2015 10:33:06 AM - SupportedFrameworkVersionRange : [4.5]

9/9/2015 10:33:06 AM -

9/9/2015 10:33:06 AM - Supported Products :

9/9/2015 10:33:06 AM - Microsoft.VisualStudio.Pro

9/9/2015 10:33:06 AM - Version : [11.0,14.0]

9/9/2015 10:33:06 AM -

9/9/2015 10:33:06 AM - References :

9/9/2015 10:33:06 AM - -------------------------------------------------------

9/9/2015 10:33:06 AM - Identifier : Microsoft.VisualStudio.MPF.11.0

9/9/2015 10:33:06 AM - Name : Visual Studio MPF 11.0

9/9/2015 10:33:06 AM - Version : [11.0]

9/9/2015 10:33:06 AM - MoreInfoURL :

9/9/2015 10:33:06 AM - Nested : No

9/9/2015 10:33:06 AM -

9/9/2015 10:33:06 AM - Searching for applicable products...

9/9/2015 10:33:06 AM - Found installed product - Microsoft Visual Studio 2012 Shell (Integrated)

9/9/2015 10:33:06 AM - Found installed product - Microsoft Visual Studio Professional 2013

9/9/2015 10:33:07 AM - The extension with ID '0d9a9c3f-5ef0-4d1f-b38e-7bc0918e291d' is not installed to Microsoft Visual Studio Professional 2013.

9/9/2015 10:33:07 AM - Found installed product - Microsoft Visual Studio 2013 Shell (Integrated)

9/9/2015 10:33:07 AM - Found installed product - Microsoft Visual Studio Express 2013 for Web

9/9/2015 10:33:07 AM - Found installed product - Global Location

9/9/2015 10:33:07 AM - Found installed product - ssms

9/9/2015 10:33:16 AM - The following target products have been selected...

9/9/2015 10:33:16 AM - Microsoft Visual Studio Professional 2013

9/9/2015 10:33:16 AM -

9/9/2015 10:33:17 AM - Beginning to install extension to Microsoft Visual Studio Professional 2013...

9/9/2015 10:33:17 AM - Install Error : Microsoft.VisualStudio.ExtensionManager.MissingTargetFrameworkException: The extension 'MicroFour StrataFrame' requires a version of the .NET Framework that is not installed.

at Microsoft.VisualStudio.ExtensionManager.ExtensionManagerService.CheckForValidDotNetFramework(IExtension extension)

at Microsoft.VisualStudio.ExtensionManager.ExtensionManagerService.CheckForInstallBlockers(InstallableExtensionImpl extension, IInstalledExtensionList modifiedInstalledExtensionsList, Boolean isNestedExtension, Boolean& olderVersionInstalled)

at Microsoft.VisualStudio.ExtensionManager.ExtensionManagerService.InstallInternal(InstallableExtensionImpl extension, Boolean perMachine, Boolean isNestedExtension, IDictionary`2 extensionsInstalledSoFar, List`1 extensionsUninstalledSoFar, IInstalledExtensionList modifiedInstalledExtensionsList, AsyncOperation asyncOp, UInt64 totalBytesToWrite, UInt64& totalBytesWritten)

at Microsoft.VisualStudio.ExtensionManager.ExtensionManagerService.BeginInstall(IInstallableExtension installableExtension, Boolean perMachine, AsyncOperation asyncOp)

at Microsoft.VisualStudio.ExtensionManager.ExtensionManagerService.InstallWorker(IInstallableExtension extension, Boolean perMachine, AsyncOperation asyncOp)[/quote]

RE: Tried New VISX with VS 2013 and Win 10

Edhy Rijo — Tue, 13 Oct 2015 21:28:02 GMT

You are welcome Joel, and thank you for the considerations.
I have always been a strong believer of the StrataFrame community and even thought for several reasons we have not been able to see new updates for SF, in my view for Windows Form, StrataFrame is one of the most complete framework and better yet, rock solid. I have applications dealing with millions of records processing and never had a call from a customer reporting a bug like memory leak or crashes due to stability of my applications.

Yes, I can't wait to see anything about SF2.0 but so far, I am very happy with my investment in StrataFrame in the long term.

RE: Tried New VISX with VS 2013 and Win 10

Joel — Tue, 13 Oct 2015 20:35:18 GMT

Thank you Ben. I really appreciate your effort in finding a solution to this issue. I also would like to send a thank you to Edhy. You went above in beyond to help get this resolved.

Blessings,

Joel

RE: Tried New VISX with VS 2013 and Win 10

Edhy Rijo — Tue, 13 Oct 2015 18:16:03 GMT

Hi All,

I am happy to inform everybody that today after several long hours today, Ben was able to duplicate the issue in my computer and fixed them all.

This was one of those issues in which VS was not reporting the right error and throwing us off the track. Without been able to debug in the computer where error was happening would have been almost impossible to identify this one.

Once Ben realized what was going on, in an hour he got a new build for me to test.

I am so happy we are back on business. Thanks Ben. :)

The fixed build is in this thread http://forum.strataframe.net/FindPost33068.aspx

RE: Tried New VISX with VS 2013 and Win 10

StrataFrame Team — Tue, 13 Oct 2015 09:27:27 GMT

Thanks to Edhy for his help letting me remote debug his Visual Studio while we modified the threading on the BOM.

The AccessViolationExceptions that several of you were receiving have been resolved. The update is posted on the releases thread.

RE: Tried New VISX with VS 2013 and Win 10

Edhy Rijo — Tue, 06 Oct 2015 08:55:21 GMT

Sorry Ben, it is still crashing.

RE: Tried New VISX with VS 2013 and Win 10

Edhy Rijo — Tue, 06 Oct 2015 08:25:48 GMT

Hi Ben,
I am testing this right now, please don't go anywhere :Wow:

RE: Tried New VISX with VS 2013 and Win 10

StrataFrame Team — Tue, 06 Oct 2015 08:08:44 GMT

I have changed several of the methods in the AddIn to test whether the ProjectItem goes stale. They should be able to test whether the IntPtr to the object is still valid. If this doesn't work, I'm going to swap out the Project and ProjectItem usage from the old EnvDTE to check the IVsHierarchy, which is what the Solution Explorer now uses to maintain the lists of the project items.

This should work; I have my fingers crossed.

I've re-attached the VSIX and DLLs on the sticky thread.

RE: Tried New VISX with VS 2013 and Win 10

Buffie — Mon, 05 Oct 2015 09:45:32 GMT

okay. thanks

RE: Tried New VISX with VS 2013 and Win 10

Edhy Rijo — Mon, 05 Oct 2015 09:08:15 GMT

Hi Terry,

Please open a new thread so this one can be dedicated to fix the issue with the support to VS2015.

RE: Tried New VISX with VS 2013 and Win 10

Buffie — Mon, 05 Oct 2015 09:05:46 GMT

I have a question about DevExpress but I am not sure I should ask it here?

RE: Tried New VISX with VS 2013 and Win 10

Michael Reese — Sat, 03 Oct 2015 08:36:40 GMT

No luck here.

RE: Tried New VISX with VS 2013 and Win 10

Buffie — Fri, 02 Oct 2015 13:47:58 GMT

I understand. Good luck. If there is anything I can do let me know.

RE: Tried New VISX with VS 2013 and Win 10

Edhy Rijo — Fri, 02 Oct 2015 12:55:57 GMT

Hi Terry,

[quote][b]Buffie (10/2/2015)[/b][hr]I was having issues with the New VSIX so I just reinstalled the old stuff and went back to VS2013 and the old Strataframe. Just could not get the new stuff to work and so I gave up.[/quote]
Thanks for the confirmation, unfortunately in my case I cannot go back that easy since I already released a version of my application using .Net 4.6 and some of the new stuff in there, so I will have to help Ben replicate this issue so it can be fixed ASAP. Also I use DevExpress and due to some previous bugs on their code I have to keep the latest version, so we need to move on.

RE: Tried New VISX with VS 2013 and Win 10

Buffie — Fri, 02 Oct 2015 10:09:38 GMT

I was having issues with the New VSIX so I just reinstalled the old stuff and went back to VS2013 and the old Strataframe. Just could not get the new stuff to work and so I gave up.

RE: Tried New VISX with VS 2013 and Win 10

Edhy Rijo — Fri, 02 Oct 2015 09:55:54 GMT

Hi Ben,
FYI, since I still have VS2013 installed, I opened one of my solutions not converted to VS2015 and try to re-build a BO and the BOM crashed at the same point as on VS2015.

Also in VS2013, I disabled the SF Extension and re-activated the old AddIn, I know they both use the same assemblies, well BOM crashed again, so my take is that there must be something in the new assemblies that is causing this crash in any solution in VS2013 & VS2015 in my system.

Is anybody else in this thread able to re-buid BO with the BOM using THE NEW VSIX?

RE: Tried New VISX with VS 2013 and Win 10

Edhy Rijo — Wed, 30 Sep 2015 11:18:21 GMT

Hi Ben,
Wow, thanks so much for checking into this and I am sorry, this is happening.

I just sent you a PM with a video link to my Solution Explorer, even though, this BOM error is happening with all my SF Solutions.

I am wonder, if the BOM exe file depends on the .Net 2.0? I may try re-installing that since when I upgraded my computer from Win7 to Win 10, I had to re-run some setups like MS SQL and MS Word and some of the SF assemblies I re-added to the GAC using gacutil.exe.

Edited: 9/30/2015 1:27pm EST
FYI: I repaired the .Net 2.0 setup in my computer, but still BOM is crashing on all SF solutions.

RE: Tried New VISX with VS 2013 and Win 10

StrataFrame Team — Wed, 30 Sep 2015 09:44:46 GMT

Alright, Edhy, I've been doing a bunch of research on this between yesterday and this morning:

Most will tell you that reinstalling VS or repairing VS will fix it:

http://www.heapoverflow.me/question-nuget-keeps-crashing-visual-studio-2013-30744059

https://bugzilla.xamarin.com/show_bug.cgi?id=27445

https://connect.microsoft.com/VisualStudio/feedback/details/621125/vs-2010-crashes-when-wpf-silverlight-designer-shown

Others will say it's due to the interaction between different add-ins and extensions:

http://stackoverflow.com/questions/9849055/nuget-crashes-vs2010-ultimate

http://stackoverflow.com/questions/13924891/visual-studio-crashes-when-removing-projects-from-c-solution-through-envdte-ad

And this has definitely been a persistent problem:

http://forum.strataframe.net/Topic18722.aspx

And then this one gave me an idea:

https://arildfi.wordpress.com/2006/11/12/ankh-and-accessviolationexceptions/

It's 9 years old, but VS still uses the same stuff internally. VS has an object model for working with Solutions -> Projects -> ProjectItems -> Sub-ProjectItems and it's possible that there is a ProjectItem hanging around in your object tree that is broken. It might have been temporarily added by VS and we've held onto the reference, or VS detached the pointer and didn't remove the item from the object model or something, but the item is now stale, and we're trying to access it. Or it could be a project item that doesn't have a containing project, so it's detached (like an object in a solution folder) or something. I'm going to comb through the EnvDTE namespace interfaces and see if I can find a way to detect stale objects and ignore them.

In the meantime, will you send me a screenshot of what your solution explorer looks like? Expand all of the nodes and then use SnagIt or something to do a scrolling screenshot so I can see the whole tree? Or email me a screen capture video where you scroll through everything expanded.

RE: Tried New VISX with VS 2013 and Win 10

Edhy Rijo — Tue, 29 Sep 2015 11:27:40 GMT

Hi Ben,

You are right, the assemblies are being loaded correctly from C:\Windows\Microsoft.NET\assembly\GAC_32.

Here is the Exception I got:
[quote]System.AccessViolationException was unhandled
Message: An unhandled exception of type 'System.AccessViolationException' occurred in MicroFour StrataFrame

AddIns.dll
Additional information: Attempted to read or write protected memory. This is often an indication that

other memory is corrupt.
[/quote]

Here is a video of the error:
http://screencast.com/t/eBbTtgnvgtc

And here is the IntelliTrace file:
www.progytech.com/downloads/sf/devenv_150929_120802.iTrace.zip

Here is the VS About info:
[quote]
Microsoft Visual Studio Enterprise 2015
Version 14.0.23107.0 D14REL
Microsoft .NET Framework
Version 4.6.00079

Installed Version: Enterprise

Architecture and Modeling Tools   00322-80000-00000-AA524
Microsoft Architecture and Modeling Tools

UML® and Unified Modeling Language™ are trademarks or registered trademarks of the Object Management Group, Inc.

in the United States and other countries.

Microsoft Visual Studio Tools for Applications 2015   00322-80000-00000-AA524
Microsoft Visual Studio Tools for Applications 2015

Visual Basic 2015   00322-80000-00000-AA524
Microsoft Visual Basic 2015

Visual C# 2015   00322-80000-00000-AA524
Microsoft Visual C# 2015

Visual C++ 2015   00322-80000-00000-AA524
Microsoft Visual C++ 2015

Windows Phone SDK 8.0 - ENU   00322-80000-00000-AA524
Windows Phone SDK 8.0 - ENU

Application Insights Tools for Visual Studio Package   1.0
Application Insights Tools for Visual Studio

ASP.NET and Web Tools   14.0.20711.0
ASP.NET and Web Tools

ASP.NET Web Frameworks and Tools 2013   5.2.30624.0
For additional information, visit http://www.asp.net/

CodeRush for Visual Studio   15.1.7.0
CodeRush for Visual Studio

Common Azure Tools   1.6
Provides common services for use by Azure Mobile Services and Microsoft Azure Tools.

CreateLayoutWizard   1.0
Create layout wizard.

DevExpress.DeploymentTool   1.0
A useful tool for deploying DevExpress assemblies.

GenerateUnitTest   1.0
Generates unit test code for methods in classes under test.

MicroFour StrataFrame   1.0
VSIntegration package for MicroFour StrataFrame V1

Microsoft Azure HDInsight HQL Service   2.0.2600.0
Language service for Hive query

Microsoft Azure HDInsight Tools for Visual Studio   2.0.2600.0
An integrated development environment for HDInsight application development.

Microsoft Azure Mobile Services Tools   1.4
Microsoft Azure Mobile Services Tools

Microsoft Azure Tools   2.7
Microsoft Azure Tools for Microsoft Visual Studio 2015 - v2.7.30818.1601

Microsoft Code Digger   0.9
Microsoft Code Digger

Microsoft.Pex.VisualStudio   1.0
Pex

NuGet Package Manager   3.2.0
NuGet Package Manager in Visual Studio. For more information about NuGet, visit http://docs.nuget.org/.

Office Developer Tools for Visual Studio 2015 ENU   14.0.23025
Microsoft Office Developer Tools for Visual Studio 2015 ENU

PreEmptive Analytics Visualizer   1.2
Microsoft Visual Studio extension to visualize aggregated summaries from the PreEmptive Analytics product.

SQL Server Data Tools   14.0.50901.0
Microsoft SQL Server Data Tools

SQL Server Integration Services
Microsoft SQL Server Integration Services Designer
Version 13.0.500.53

Visual Studio Tools for Universal Windows Apps   14.0.23309.00 d14oob
The Visual Studio Tools for Universal Windows apps allow you to build a single universal app experience that can

reach every device running Windows 10: phone, tablet, PC, and more. It includes the Microsoft Windows 10

Software Development Kit.

Workflow Manager Tools 1.0   1.0
This package contains the necessary Visual Studio integration components for Workflow Manager.

Xamarin   3.11.837.0 (f10676f)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.

Xamarin.Android   5.1.5.3 (f98871a95a479f6d71b3067b7e5834d41fcb2118)
Visual Studio plugin to enable development for Xamarin.Android.

Xamarin.iOS   8.10.4.0 (6db87c53c073f4af2f5247fb738a27ea08c094fd)
Visual Studio extension to enable development for Xamarin.iOS.

Xamarin.iOS Unified Migration   1.0
Automated migration for Xamarin iOS Classic projects to Unified

Xamarin.TestCloud.Integration   1.0
Early preview of Xamarin Test Cloud integration

XtraReports package   1.0
XtraReports package[/quote]

RE: Tried New VISX with VS 2013 and Win 10

StrataFrame Team — Tue, 29 Sep 2015 11:00:59 GMT

You can use your VS2015 to debug your VS2015. When you start up a new session and attach to devenv.exe, check the Modules window. It will list the location where all of the modules have been loaded. It shouldn't be pulling from C:\Windows\assembly because that's the .NET 2.0 location, so we probably don't have to worry about removing them.

While you're at it, will you send me the output of the Help -> About Microsoft Visual Studio -> Copy Info? There might be something in there that could give us a clue as to why you're getting the access violation exception in the BOMapper.

And yes, the GAC solved several things about DLL Hell, but it introduced it's own version of DLL Hades ;)

RE: Tried New VISX with VS 2013 and Win 10

Edhy Rijo — Tue, 29 Sep 2015 10:55:15 GMT

Hi Ben,

This is DLL hell coming back to me :D

I deleted the dll from here: C:\Windows\Microsoft.NET\assembly\GAC_MSIL

The ones from C:\Windows\assembly I am not able to remove or delete, I will get "Access Denied" error. My guess is that those were installed by the SF setup and windows installers then cannot be removed manually, not even using gacutil /uf or ur, so I think the BOM is actually using those DLLs in C:\Windows\assembly instead of the correct ones installed in C:\Windows\Microsoft.NET\assembly\GAC_32.

I don't know if anybody else is able to reproduce this issue. Can you verify if you have in your test VM the dlls in C:\Windows\assembly ?

RE: Tried New VISX with VS 2013 and Win 10

StrataFrame Team — Tue, 29 Sep 2015 10:43:38 GMT

Those are the ones built by the build server, so they are x86, and they will end up in C:\Windows\Microsoft.NET\assembly\GAC_32 after you install them with gacutil. You might clear out the ones still in C:\Windows\Microsoft.NET\assembly\GAC_MSIL if you have any. A just for grins, remove the ones from C:\Windows\assembly, since those are the .NET 2.0 ones that will no longer be used.

RE: Tried New VISX with VS 2013 and Win 10

Edhy Rijo — Tue, 29 Sep 2015 09:38:24 GMT

Hi Ben,

Thanks for the explanation, I will try it right now.

Ben, it is still crashing on me. Let's clarify where the DLL path should be registered in my system Windows 10 Pro 64 bits.

I have old versions of the AddIns.dll and Extensibility.dll in C:\Windows\assembly

Now, your dlls included in the zip package will be registered in C:\Windows\Microsoft.NET\assembly\GAC_32. Is this correct or should they replace the ones in C:\Windows\assembly ?

RE: Tried New VISX with VS 2013 and Win 10

StrataFrame Team — Tue, 29 Sep 2015 09:15:34 GMT

OK, Edhy, the best I can tell from the Intellitrace that you sent me is that the exception is being thrown when the code tries to access the ProjectItem.Name property. All of VS is COM objects, so that means the __ComObject has become unstable and is throwing that memory corruption exception. I have not been able to reproduce it here. The BOMapper writes the partial classes with no problem. I did however, get a few InvalidOperationExceptions for accessing a disposed object when the timer fires to try to close the results window (we had to add that because VS 2008 had a bug that wouldn't allow you to close the window once it was opened modally).

So, I have changed the ProjectItem.Name access to use the FileNames collection instead and I posted the updated DLLs back to the sticky thread where the VSIX is posted.

You guys give it a try and let me know how it works.

RE: Tried New VISX with VS 2013 and Win 10

Edhy Rijo — Mon, 28 Sep 2015 11:08:47 GMT

Hi Ben,
Hope you are around and well.

Please let us know how is this update coming up, we really need to get this issue with the BOM fixed to be able to continue working on our projects.

Thanks!!!