Everytime after generating code in the VS integrated LLBLGEN experience, VS crashes.

VS Version 14.0.25123.00 Update 2 .NET Version 4.6.01038 LLBLGEN Version 5.0.0 RTM (Apr 25)

Exception from App Eventlog:

Application: devenv.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.NotImplementedException at EnvDTE.Project.get_FullName() at SD.LLBLGen.Pro.VSNet.LLBLGenProVSIXPackage.LLBLGenProVSIXPackage.AddVsNetProjectsToSolution(System.Collections.Generic.List1<System.String>) at SD.LLBLGen.Pro.VSNet.LLBLGenProVSIXPackage.EditorPane._integrationController_VSNetProjectsCreated(System.Object, SD.LLBLGen.Pro.VSNetIntegrationSupport.VsNetProjectsEventArgs) at SD.Tools.BCLExtensions.SystemRelated.EventExtensionMethods.RaiseEvent[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](System.EventHandler1<System.__Canon>, System.Object, System.__Canon) at SD.LLBLGen.Pro.Gui.Classes.VisualStudioIntegrationController._mainWindowObject_VSNetProjectsCreated(System.Object, SD.LLBLGen.Pro.VSNetIntegrationSupport.VsNetProjectsEventArgs) at SD.Tools.BCLExtensions.SystemRelated.EventExtensionMethods.RaiseEvent[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](System.EventHandler1<System.__Canon>, System.Object, System.__Canon) at SD.LLBLGen.Pro.Gui.Controls.MainWindow.RaiseVsNetProjectsCreated(System.Collections.Generic.List1<System.String>) at SD.LLBLGen.Pro.Gui.Classes.GuiController.PerformGenerateSourceCodeAction() at SD.LLBLGen.Pro.Gui.Controls.ProjectExplorer.<BuildActionPerBarItemCache>b__8c() at SD.LLBLGen.Pro.Gui.Controls.ProjectExplorer._mainBarManager_ItemClick(System.Object, DevExpress.XtraBars.ItemClickEventArgs) at DevExpress.XtraBars.BarManager.RaiseItemClick(DevExpress.XtraBars.ItemClickEventArgs) at DevExpress.XtraBars.BarItem.OnClick(DevExpress.XtraBars.BarItemLink) at DevExpress.XtraBars.BarButtonItem.OnClick(DevExpress.XtraBars.BarItemLink) at DevExpress.XtraBars.BarItemLink.OnLinkClick() at DevExpress.XtraBars.BarButtonItemLink.OnLinkClick() at DevExpress.XtraBars.BarItemLink.OnLinkAction(DevExpress.XtraBars.BarLinkAction, System.Object) at DevExpress.XtraBars.BarButtonItemLink.OnLinkAction(DevExpress.XtraBars.BarLinkAction, System.Object) at DevExpress.XtraBars.BarItemLink.OnLinkActionCore(DevExpress.XtraBars.BarLinkAction, System.Object) at DevExpress.XtraBars.ViewInfo.BarSelectionInfo.ClickLink(DevExpress.XtraBars.BarItemLink) at DevExpress.XtraBars.ViewInfo.BarSelectionInfo.UnPressLink(DevExpress.XtraBars.BarItemLink) at DevExpress.XtraBars.Controls.CustomLinksControl.OnMouseUp(System.Windows.Forms.MouseEventArgs) at DevExpress.XtraBars.Controls.CustomPopupBarControl.OnMouseUp(System.Windows.Forms.MouseEventArgs) at System.Windows.Forms.Control.WmMouseUp(System.Windows.Forms.Message ByRef, System.Windows.Forms.MouseButtons, Int32) at System.Windows.Forms.Control.WndProc(System.Windows.Forms.Message ByRef) at DevExpress.XtraBars.Controls.CustomControl.WndProc(System.Windows.Forms.Message ByRef) at System.Windows.Forms.Control+ControlNativeWindow.OnMessage(System.Windows.Forms.Message ByRef) at System.Windows.Forms.Control+ControlNativeWindow.WndProc(System.Windows.Forms.Message ByRef) at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr, Int32, IntPtr, IntPtr)

Actual VS Crash from App Eventlog:

Faulting application name: devenv.exe, version: 14.0.25123.0, time stamp: 0x56f22f32 Faulting module name: KERNELBASE.dll, version: 10.0.10586.162, time stamp: 0x56cd55ab Exception code: 0xe0434352 Fault offset: 0x000bdad8 Faulting process id: 0x98a0 Faulting application start time: 0x01d1a6afad728335 Faulting application path: C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\devenv.exe Faulting module path: C:\WINDOWS\SYSTEM32\KERNELBASE.dll Report Id: 4bab764a-0bb2-41da-ab47-c9b93d5f63d1 Faulting package full name: Faulting package-relative application ID:

Let me know if I can provide you more info.

Cheers Michel

You installed the vs.net extension during installation or did you uncheck that and use v4.2's vs.net extension? Anyway, I'll try to reproduce it.

Can't reproduce it. Code generates fine in v5.0 inside VS.NET, projects are added properly. (2015 u2) Still think it's a mixup between v4.2 and 5.0 somehow...

Anyway, for the mean time, please use the standalone designer.

What I did: I created a new solution, add a console app project. Added an llblgenproj file to the solution. Save.

Then opened the llblgenproj file, pressed F7, code generates, projects are added properly. Changed something, regenerated, worked fine.

So not sure what happens... THe error is very weird, ProjectName property on EnvDTE 'not implemented', that is strange...

I'll try on another VM.

Other box, vs.net 2015 U2, can't reproduce it either. same steps.

I installed the extension during the installation of LLBLGEN, not afterwards. Any logging or anything that I can enable?

I have updated from 4.2, so it was not a clean install.

It's an odd error, as if there's something broken inside vs.net, as the EnvDTE property returns 'not implemented' which is strange. The code to add the project is the same in the v4.2 extension as in the v5 extension, so nothing changed there. If it worked in v4.2 and not in v5, it's even more strange....

If you reproduce the steps I described above, i.e. an empty solution, add a console app, add your llblgen proj file, save(!), generate into some new folder and see whether that adds the projects or not...

I did exactly that and it didn't crash... Interesting.

I might try throwing away the current (llblgen) project (which was upgraded several times) and just use a new blank one...

Thanks Michel

I don't think that's necessary, try first removing the .vs folder in your solution's folder. (it's hidden). You have to reset the startup project but that's it. Or remove the .suo files (also hidden), which might be a problem. The llblgen pro project (llblgenproj file) isn't the cause of this, it's the communication between the extension and vs.net itself (it tells vs.net to load these projects AB and C into the solution) which goes wrong...