Lazycoder

SQL Reporting services integration with visual studio

What a piece of crap. I’m so tired of VS, it’s the source of more delays in my work than anything else.

I get an eval copy of SQL Reporting services yesterday at DevDays 2004. Go to work and install it. Do the reboot shuffle. Open up visual studio, create a “new report project” and what do I get? Some cryptic error message about the “Microsoft.VisualStudio.Shell.Interop”.

The full text of the message is this.
“The located assembly’s manifest definition with name “Microsoft.VisualStudio.Shell.Interop” does not match the assembly reference.”

How do you think this will affect adoption at the large research center where I work if I’m the only person on my floor that has an opinion on this technology? I think it’s getting a big thumbs down if I can’t even WRITE A FRIGGIN’ REPORT to try it out.

I have no idea how to fix this, I’m not even sure what’s broken. Has some visual studio plug in overwritten my interop assembly? Is the problem in the reporting services plug in? If I recommend it to my boss will he have the same problem? Will the sys admins have a bunch of problems installing it on the servers? I’ve got the most up to date .NET Framework installed. I’m not running any beta software. This kind of crap is frustrating.

update: found out that someone else has had the same problem.

update to the update: Now the IDE is telling me that the application for project type rptproj is not installed. WTH?