Bug 13360 – System.NotImplementedException in Build window output when used along with Web Essentials

Visual Studio 2013 Ultimate, Update 3 RTM Windows 8.1 Web Essentials 2014 for Update 3 (v2.3) Visual D v0.3.39 beta 2 Everytime I build the project/solution the Build output window contains the System.NotImplementedException with the following stack trace: Debug\Set01.exe not up to date: link dependency file D:\Dev\Learn\D\Programming in D\Set01\Debug\Set01.lnkdep does not exist ------ Build started: Project: Set01, Configuration: Debug Win32 ------ Building Debug\Set01.exe... Converting debug information... ========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ========== 2014-08-23 00:38:49: An exception was thrown when Web Essentials: Updating Bundles...: System.NotImplementedException: The method or operation is not implemented. at EnvDTE.Project.get_Collection() at MadsKristensen.EditorExtensions.ProjectHelpers.GetChildProjects(Project parent) at System.Linq.Enumerable.<SelectManyIterator>d__14`2.MoveNext() at System.Linq.Enumerable.<UnionIterator>d__88`1.MoveNext() at System.Linq.Enumerable.WhereEnumerableIterator`1.MoveNext() at MadsKristensen.EditorExtensions.BundleFilesMenu.<UpdateAllBundlesAsync>d__12.MoveNext() 2014-08-23 00:38:49: An exception was thrown when Web Essentials: Updating Sprites...: System.NotImplementedException: The method or operation is not implemented. at EnvDTE.Project.get_Collection() at MadsKristensen.EditorExtensions.ProjectHelpers.GetChildProjects(Project parent) at System.Linq.Enumerable.<SelectManyIterator>d__14`2.MoveNext() at System.Linq.Enumerable.<UnionIterator>d__88`1.MoveNext() at System.Linq.Enumerable.WhereEnumerableIterator`1.MoveNext() at MadsKristensen.EditorExtensions.Images.SpriteImageMenu.<UpdateAllSpritesAsync>d__f.MoveNext()

I've tried it with the version for VS2012, and it does not happen there. For me, Web Extensions with VS2013 Shell crashes when loading any solution. There are also other reports for Web Extensions crashing, so I'm unsure I can test this. The cause for the exception is that the automation model is only implemented to the point that reports like in this issue do not appear. I guess I could implement the requested function, but it will probably hit the next one later.

I am interested in addressing this issue. Since I am able to get the exception and along with testable VS2013 I can take this bug item and work it out if you like.

I guess it will need some back and forth with fixing and testing. Here is a first guess: https://github.com/D-Programming-Language/visuald/releases/tag/v0.3.39-beta3

Hi Rainer, I guess you are right. The extension itself is in D Language and I am just a beginner, I doubt I will be able to troubleshoot this issue in a short time. I went through the code, the following is my summary after the first view: * I traced the Not Implemented exception by trying to see the location of the Methods causing that exception in the VisualD code (Project.Collection, Project.ExtenderCATID and so on) to the file VisualD/project/automation.d *. automation.d has 55 not implemented methods and the whole project seems to have 177. *. Strangely the 3 Collection methods are not returning "E_NOTIMPL", so either I am looking at the wrong location or one of the intermediary method calls is throwing that exception?

(In reply to vijay from comment #4) > Hi Rainer, > > I guess you are right. The extension itself is in D Language and I am just a > beginner, I doubt I will be able to troubleshoot this issue in a short time. Yeah, building Visual D has some complications... > I went through the code, the following is my summary after the first view: > > * I traced the Not Implemented exception by trying to see the location of > the Methods causing that exception in the VisualD code (Project.Collection, > Project.ExtenderCATID and so on) to the file VisualD/project/automation.d > > *. automation.d has 55 not implemented methods and the whole project seems > to have 177. I hope to not have to implement them all. My current goal is to not cause errors elsewhere. Some implementation is just there to mute the NuGet Package Manager. > > *. Strangely the 3 Collection methods are not returning "E_NOTIMPL", so > either I am looking at the wrong location or one of the intermediary method > calls is throwing that exception? I implemented the Collection methods just today. The one that appeared in the call stack seemed to be pretty independent of the rest, so it was not too difficult. Have you tried the new beta? Is it now failing in a different method?

Hi, I am not getting any more exception after installing v0.3.39-beta3. Thank you!