Can't open component in VS2012 (64 bit)



installation of the component worked fine and I can drag it to the canvas. But when I open it I do get the following error message:

Value of 'null' is not valid for 'stream'. (Microsoft Visual Studio)

Program Location:

at System.Drawing.Icon..ctor(Stream stream, Int32 width, Int32 height)
at System.Drawing.Icon..ctor(Stream stream, Size size)
at Microsoft.SqlServer.IntegrationServices.Designer.Common.ImageSourceHelper.GetIconFromResource(Assembly assembly, String resourceName, Boolean isLarge)
at Microsoft.DataTransformationServices.Design.DesignUtils.ExtractManagedBitmap(String fileName, String resName, Boolean large)
at Microsoft.DataTransformationServices.Design.DesignUtils.ExtractBitmap(String fileName, String iconResource, Boolean isNative, Boolean large)
at Microsoft.DataTransformationServices.Design.PipelineUtils.GetComponentIcon(IDTSComponentMetaData100 componentMetadata, IServiceProvider serviceProvider)
at Microsoft.DataTransformationServices.Design.FunctionLevelMappingUI..ctor(FunctionLevelComponentUI componentUI, IUserPromptService promptService)
at Microsoft.DataTransformationServices.Design.FunctionLevelComponentUI.EditImpl(IWin32Window parentControl)
at Microsoft.DataTransformationServices.Design.DtsComponentUI.Edit(IWin32Window parentWindow, Variables variables, Connections connections)

I have a 64 Bit OS, maybe that is a problem?

Any ideas/suggestions?



rbeard wrote Jan 29, 2014 at 4:49 AM

This is a little late, but in case it helps anyone.

To resolve this, I added an IconResource to the DtsPipelineComponent attribute like so:

[DtsPipelineComponent(DisplayName = "Azure Blob Storage Destination", Description = "Writes data to a file in Windows Azure Blob Storage", ComponentType = ComponentType.DestinationAdapter, IconResource = "SSISAzure.BlobStorageDestination.Resources.Icon1.ico")]

This applies to both the Source and Destination components.

Add an Icon to the each project.
Set the build action of the new icon (icon1.ico) to embedded resource.
Rebuild and redeploy using the deploy_ssisazure_components.bat file.

wrote Mar 23, 2014 at 3:05 PM

Leeds_DBA wrote Mar 23, 2014 at 3:06 PM

It's worth noting, that while you can't open the GUI for this component, you can still edit the properties (via property window) ok.


wrote Mar 26, 2014 at 12:07 PM

wrote Jan 26, 2015 at 4:12 PM

wrote Aug 31, 2015 at 11:01 PM

rloone wrote Jun 5, 2016 at 3:50 AM

This appears to be an issue for a number of custom components.