3

Closed

Deploy SSIS Packages - no Deploy (BIDS Helper) - version 1.4.2.1

description

I've seen another post here where this issue was resolved, but the last post didn't state what the fix was. I installed 1.4.2.0 and the Deploy (BIDS Helper) option did not appear in the Package Property page, so I uninstalled 1.4.2 and installed 1.4.2.1 and I still get the same error when trying to Deploy: "Error : Deployment FilePath is not set. Right click on the project node and set the FilePath property." I don't see others posting about this problem - so I wonder what the fix was.
 
I'm running:
XP Pro SP2
VS2005 Version 8.0.50727.762 (SP.050727-7600)
Microsoft Visual Studio 2005 Team Edition for Software Architects
.NET Framwork 2.0.50727 SP1
BIDSHelper Version 1.4.2.1
Closed Mar 21, 2010 at 5:06 PM by furmangg
I believe we have fixed this. It will be in the next release which follows 1.4.2.1.If anybody would like to contact me by clicking furmangg and sending me an email asking for a private build in the meantime so you can test out that our fix worked for you, feel free.

comments

ranomore wrote Aug 27, 2009 at 7:10 PM

I don't see this either. I have BIDS 2005 and 2008 installed, with VS Pro 2005 also installed, with BIDS Helper 2008 1.4.2.1.

jvcampbell wrote Sep 30, 2009 at 9:43 AM

I've got the same problem with BIDS Helper 2008 1.4.2.1. - I've only got VS 2008 installed on my machine.

bobsilva23 wrote Nov 18, 2009 at 6:26 PM

Same problem.... BIDS Helper 2008 1.4.2.1 and VS 2008...

Anyone hear anything back on this?

furmangg wrote Nov 21, 2009 at 10:40 PM

I've just checked in a change to the source code that will hopefully work for everybody. And if it doesn't, it will spit out a debug file to the following path which you can send us via attaching it to this issue:
C:\Documents and Settings\<username>\Local Settings\Temp\BidsHelperDeploySSISPackagesPropertiesMenuDebugLog.txt

If anybody wants a quick private build of this change to make sure it's working for you before we release this change, contact me.

furmangg wrote Nov 21, 2009 at 11:06 PM

should be fixed as described a second ago in release 1.4.2.2

Sign in to add a comment