Sorry for the delay in getting back with you. I actually missed this post.



Please answer one question for me as it might give us a clue. You have been a user for a while, so what changed on this development machine between when things worked and when it stopped?



This is one of the most frustrating errors that I have seen as I have figured out what piece is failing, but Microsoft could not give me any straight answers (or to this point ... ANY answers). I was excited the other day because I could debug it and I thought I would be able to isolate the issue....but it went away and started working again!



So it is definitely environmental. Because something within my environment changed that allowed be to get to the DTE.



I had the same issue with a Macro that we had created in house. When you create a macro, it hands you the DTE object...so...you would think that VS would give you a valid instance to work with...but in my case it failed. I moved it over to the Add-In and it worked (makes no sense). I also had the issue with the BO Mapper shortly afterwards (the machine I am working on is a new development machine...thus the newness of the issue). But after debugging and changing some things...it started to work. I didn't change any drastic, just rebuilt the extensibility solution several times (maybe like 20).



I will see if I can reproduce again. But this definitely environmental and we have not yet figured out the root of the cause...sorry I will see if I can get it to happen again on my side.

I had this and as I posted a reinstall fixed it, luckily. It was also after an install of the InstallAware trial. I didnt think it a factor at the time, but this post made the lightbulb go off and I figured you would like another data point.

Good luck with Microsoft, after 3 hours on the phone with them trying to troubleshoot a WDAC error on my machine, the fix was of course "reload your OS".

Keith Chisarik

LOL...yeah, I am not holding my breath! But I think this is starting to shed some light.



Edhy, if you read this post would you comment if this was after your IntsallAware install as well? Thanks!

Hi Trent,



I honestly don't remember if I did something with IA at the time of getting this problem, but that may be the case since I also use IA and may have probably install an update which at any case will simple remove the current installation and install the new one



In my case re-installing the .Net 2.0 fixed the problem, don't know if IA could mess with that, but at least now we all have another factor in this case "InstallAware". Probably you could setup a VPC and play with this installing IA.



FYI, my version of IA is: 8.01 (Build Ame - Rej.RTM, 110408).

Edhy Rijo

Thanks for the update, Edhy!

Trent,

Sorry I am just getting back to you. I ended up doing a repair of Visual Studio 2008 (praying I did not have to reformat the machine!). I reinstalled everything (Strataframe and Infragistics NetAdvantage 2009) except InstallAware. Went back to my project, opened the BOM and everything worked!



Now I am a little gun shy about installing InstallAware 9 back on this machine unless I can exclude that VS add-in option (or get a separate machine to create IA packages...ugh!). I may just try installing IA to see if I can recreate the error (now that I know what is needed to get back to Kansas :w00t.



Doug

Hi Doug,



In your case, if you have the time I may do just that, install IA and do the following:

1 - Test the BOM

2 - Reboot the computer

3 - Test again the BOM



That may give us a better clue. FYI, I am using IA in the same working computer with VS and SF.

Edhy Rijo

LOL...I am glad that you mentioned the InstallAware piece. I had been scratching my head profusely (and slapping myself in the face ever now and then) up until that point! I knew that there had to be some common denominator here.



On a good note, I am actually running, with success, at this point with all installed. So it is possible, just painful

Updated...

After installing VS2010 in Windows 7 x64, I installed InstallAware 8.1 and again the BOM stop working with the same errors explained here.

I had to reinstall the .Net 2.0 "en_net_framework_sdk_20_x64.exe" and that fixed the problem with the BOM.

Edhy Rijo

Yeah, I've taken to unchecking the "Visual Studio Add-In" component of InstallAware to avoid any potential issues here. We still haven't gotten official confirmation/denial that would confirm InstallAware as the culprit of these issues, but it follows suit with the experience of most here, as well as Trent and myself.