Intellisense is broken on 64 bit Windows when using mixed (i.e. managed C ++) assemblies

This is more annoying than anything else, but I don't have Intellisense working when I use any of my custom web controls on .aspx / .ascx pages. Intellisense in standard controls <asp:...>

works fine, as it does in all code files, etc.

I'm pretty sure this is caused by Visual Studio trying to parse the bin folder of the website for custom web controls and throw the flex form when it hits one of the DLLs - a (mixed mode) 64-bit managed C ++ assembly ( I'm running Win 7 64-bit). It looks like Visual Studio is trying to load this assembly and it fails, due to VS being a 32-bit application.

Anyone have any ideas how to get around this? I was looking for an option to force VS to ignore a 64-bit assembly (there are no web controls in it - they exist in a different standard assembly), but alas, nothing was found.

Note: this is VS 2010, but I would guess it would be a problem in any version.

+2


a source to share





All Articles