Interop Assemblies aren't Auto-Refreshing in VS2005

November 06, 2005 @ 11:31 pm

Looks like creating COM Interop projects with ASP.NET just got a whole lot less pleasant with Visual Studio 2005. In VS.2003 if you updated the underlying COM server and then rebuild and refreshed the project that contained in imported Interop assembly the interop assembly automatically refreshed itself to provide the updated COM interface.

I can no longer get that to work. The only way to get the assembly to work is to physically remove it and then add it back into the project…

This is definitely a few steps backwards. Not that I advocate using COM in ASP.NET projects anyway, but this is still a PITA when you do need to do it. I’m working on some Fox demos at the moment where a Web Service needs to talk to a Fox Com object to provide the data layer, and any change to the COM server requires removing and reading the COM reference. This gets old real quick especially knowing that this used to be automatic by a recompile.

I guess it's possible to add some MSBuild logic to the project to make this happen automatically.

Now playing: Rollins Band - You Didn't Need

Feedback for this Weblog Entry

# r you serious?
by Paul Oak November 07, 2005 @ 12:33 am

Using iTunes for playing mp3s?

# re: Interop Assemblies aren't Auto-Refreshing in VS2005
by Rick Strahl November 07, 2005 @ 1:19 am

I've used all sorts of players and ITunes is the only thing that works right with my IPod. ITunes is not great, but no worse than most of the other players. I'm open to suggestions...

Actually most of the time I use an old version of Music Match (V8). The old Music Match players were great, but later versions are bloated crap. I like Music Match Radio, which as far as I can tell has the best radio stations for the music I listen to. Also music match has good audio import tools - importing WAV files to MP3 etc at better quality than most dedicated audio tools.

Don't get me started on this whole audio player debate. All of them are huge hogs for something so simple as a small database application <g>...

# re: Interop Assemblies aren't Auto-Refreshing in VS2005
by AsbjornM November 07, 2005 @ 3:39 am

Kinda ok actually, I hated the interop-refresh, so instead I created interops manually using tlbimp, so the developers all had the same interop-assembly.
Of course, if you create the com object and the .net project at the same time you need some way to refreash that interop, but hey, who's doing that?
(btw, look at mediamonkey for an decent player)

# DotNetSlackers: Interop Assemblies aren't Auto-Refreshing in VS2005
by DotNetSlackers Latest ASP.NET News October 10, 2006 @ 10:29 pm