SQL Server 2008 RC0 x86 on XP SP2
When I create a Script Task and select Visual Basic 2008, the Properties and References nodes do not appear in the project tree. When I try to add a reference to a custom assembly, I get the error "No Visual Studio template information found." I followed the event viewer's advice and ran vsta /installtemplates only to find out the appropriate switch is /setup. That made no difference anyway, so I tried devenv /installtemplates, which still didn't help. I then installed RC0 on another machine (Windows 2003) with no other Visual Studio installation and the same problem prevails. One thing to note is that I did not install any instance features, and I did not install the Microsoft Sync feature. |
| the_chad Friday, August 01, 2008 7:23 PM |
did you add your custom assembly to the global assembly cache?
hth
|
| Duane Douglas Monday, August 04, 2008 3:23 AM |
You might want to check this thread, as the error message seems related:
http://forums.microsoft.com/Forums/ShowPost.aspx?PostID=3289078&SiteID=1
|
| jwelch Monday, August 04, 2008 12:50 PM |
Yes, it is in the GAC, and I am not saving objects to "DTS" variables. It seems to be a problem with the environment, as the properties and references nodes are not in the project explorer tree. Is everyone else able to add a VB.NET Script Task and see these? I would gladly use C# (this same problem does not occur with C# tasks), but since I am converting SSIS 05 Projects that is not an option. In addition not all developers here are C# Savy. Please Help!! |
| the_chad Monday, August 04, 2008 3:30 PM |
Is there someone out there with a spare couple of minutes that would be willing to try and recreate this problem?
If so, create an SSIS 2008 project (or open an existing one) and add a script task to it. Select Visual Basic 2008 as the language and click Edit Script. In the Project Explorer do you see "Properties" and "References"? Try to add a reference byright-clicking the top node in the Project Explorer, which is probably named something like "scripttask_{GUID}", and select Add Reference. Click the Browse tab and find a .net dll to add. Add it and please tell me if you have the same problem I am having.
THANKS!!!!
P.S. If you do all the same steps above, but select Visual C# 2008 as the language, everything will work fine. |
| the_chad Monday, August 04, 2008 9:14 PM |
I have installed RTM and this is still an issue. Can someone else please check this out and see if you are having the same issue? I have installed this on two different machines and received the same results. |
| the_chad Friday, August 08, 2008 5:15 PM |
Has no one else had this problem? Is this forum dead, or has it been relocated? |
| the_chad Thursday, August 14, 2008 2:45 PM |
ANYONE??
All I need is just a simple yes or no!!! This is a make or break for our SSIS 08 implementation and I am almost out of time for the final decision... |
| the_chad Thursday, August 21, 2008 10:18 PM |
I get the same results you are describing. However, it doesn't occur if I reference a custom dll that is in the GAC. Why not just GAC it, since this is likely to be needed for deployment anyway?
|
| jwelch Thursday, August 21, 2008 10:40 PM |
I've got an even better answer 
Double-click My Project in the project tree. Go to the References tab and add it there. No error, everything appears to work fine.
|
| jwelch Thursday, August 21, 2008 10:42 PM |
I did that, and I got the error, but the reference seemed to be added, as I was able to use it. However, when I opened the script task editor againafter testing it, the reference disappeared. I tested this will several different assemblies, including ones built in VS08 and VS05. All of theseassemblies were given strong names and added to the GAC. Script Tasks in C# do not have this problem.
It looks like SSIS 08 has some growing to do before we can implement it.
|
| the_chad Monday, August 25, 2008 9:30 PM |