I have been working on creating SSIS packages using Sql Server Data Tools in Visual Studio 2012.

I was running into a problem where I could run a package in Visual Studio, but it would not run when deployed to Integration Services on the same machine.  What's the difference?

My package is using an ODBC connection using a Data Source setup on my machine using a 32-bit driver.

Behind the scenes SSIS runs DTExec.exe to execute the packages.  The trick is that on 62-bit installations there are two different locations for DTExec.exe; one for 32-bit version and another for 62-bit version.

So to summarize... I've got an SSIS package that uses a 32-bit ODBC data source.  When I run in Visual Studio all is fine because Visual Studio uses 32-bit.  When I run in SSIS, I get errors because SSIS is calling a 64-bit version of DTExec which is then looking for my ODBC connection in the 64-bit Data Sources setup on the machine, which does not exist.

SO... I need to tell Sql Server SSIS to use the 32-bit DTExec even when running under 64-bit.

Don't worry, I am confusing myself at this point!  But let's just get to the solution...

The Fix

The fix for me was to edit the Registry settings for Sql Server and point the DTS path to the location of the 32-bit version of DTExec.

The registry setting for Sql Server 2012 is located in...

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\110\SSIS\Setup\DTSPath

Note: Edit registry at your own risk!

The default value is...

C:\Program Files\Microsoft SQL Server\110\DTS\

I changed it to...

C:\Program Files (x86)\Microsoft SQL Server\110\DTS\

Summary

There can be platform conflicts between data sources and the environment they eventually are called in.  This little trick helped me get my SSIS packages running again.  I hope it helps you, too.

Finally located the VS 2012 installer for Business Intelligence tools.  Now I can create SSIS packages in VS 2012 with everything else!

http://www.microsoft.com/en-us/download/details.aspx?id=36843

Found this nice little tool for mounting ISO images without having to burn DVD's...

http://www.slysoft.com/en/virtual-clonedrive.html

Visual Studio 2012 has some great features for building new apps, but you may run into some issues with pre-existing applications.  In my particular case, I found that the "Web Site" project type will no longer support Web Deployment projects.

So, when I load up my solution in Visual Studio, I get an error about the Web Deployment project not being recognized.

"Web Application" projects are the ideal approach, and yes, I want to upgrade someday.  But that day is not today.  Today I need to get my project built using the same Web Deployment project file.

I know the Web Deployment project type is not available for VS 2012, but if I could at least build the project using the ".wdproj" file as a build script, I would be happy.

Here is how I created a work around...

Explanation

First, Web Deployment projects are nothing more than an MSBuild project file with some custom build "targets".  In VS 2010, when you right-click on the Web Deploy project file and choose "build project", it would run MSBuild.

So... if we enable the build targets and still run MSBuild with the project file, we should be able to build our project.

Install Web Deployment Projects 2010

The Web Deployment project installer is still available from Microsoft.  When you install, it will add the build targets to this directory...

C:\Program Files (x86)\MSBuild\Microsoft\WebDeployment\v10.0

For clarity, I copied this directory to a new directory and called it "v11.0"

In this copied directory, open the file Microsoft.WebDeployment.targets in a text editor, and replace all instances of "VisualStudio\v10.0" with "VisualStudio\v11.0"

That should be enough to get the build targets working.

Update Web Deployment Project File

Now locate your Web Deployment project in Windows Explorer.  Open the .wdproj file in a text editor.

Near the bottom, there is a line that looks like this...

  <Import Project="$(MSBuildExtensionsPath)\Microsoft\WebDeployment\v11.0\Microsoft.WebDeployment.targets" />

Change the "v10.0" to "v11.0" to point to your new targets file.

Run MSBuild

Run the Visual Studio command prompt and enter the following command (update paths for your project location)...

msbuild [path/to/your/site.wdproj] /property:Configuration=Release

/l:FileLogger,Microsoft.Build.Engine;logfile=[your/deployproj/dir/BuildLiveLog.log]

I created a .bat file to save keystrokes, and I just copy the batch file to other projects and update the paths as needed.

Hope this helps someone else out there.

[Edit 10/31/2012]
Gave it a second attempt today.  The links to the license agreement did work this time around, but there still was no encryption indicator on the page.  
[End Edit]

Windows 8 was released this week.  I've been waiting for this in hopes of pumping some life into my old Vista Ultimate system.  

So, I went to Windows 8 web site, and I came across some user experience things that may be confusing users.  There is a button that says "Download Pro for $39.99", which I click anticipating a new screen with further instructions.  Instead, I got a dialog box asking me to save something called Windows 8 Upgrade Assistant to my PC.

Nothing on the page said anything about Download Assistant, I thought I was going to make a payment, download, and go.  Already I am having to make a decision about whether downloading this is a good idea.  My guards are up now, because it wasn't what I was expecting.  It may be Windows phobia, but surely I'm not the only one who raises an eyebrow when a download dialog pops up.  After a long history of bugs and viruses, download trust-ability is important.  So, I almost hit Cancel because the download dialog makes me double-check.  Is this safe? Am I on the right web site?  Did I come from a link in an email?  Am I going to regret this?

[Edit: After reviewing the page, there is a description of the Download Assistant if you scroll below the visible screen.]

After consideration, I took the risk and installed the Download Assistant.  The Assistant is actually pretty cool. This little utility will do a scan of your system and let you know what programs and devices will be able to work on Windows 8.  Nice.

After completing the system check you will have a chance make your Order.  I have the option to download Windows 8 for $39.99, and add a DVD version for $14.99.  This is confusing because on the web site the Buy Now page says I can have Windows 8 shipped to me for $69.99.  Hmmm.... $39.99 + $14.99 = $54.98. So we're off by $15.01. Math error? As a user this is what goes through my head... Did I do something wrong? Did I download the right thing?  Did I miss something?  Well, what the heck, I might as well get the DVD now and save 15 bucks! But if I do, will they stick it to me later in the checkout process?

Something else, on the checkout page of the Download Assistant there is a link that says "More about downloads over metered Internet connections".  That sounds important.  Since the download is 2GB, I should probably see what Microsoft has to say.  It takes you here.  As of Saturday, Oct. 27 2012, that page provides absolutely no such information!  Thanks for the help!

Next, the Assistant asks me for Billing Address.  I am starting to feel uncomfortable.  I am running an app, not a web site.  The information is getting more personal, but I have NO security indicators.  Since I am not is a web browser, I have no padlock icon, no SSL indicators, not even a web address with "https://".  Are they going to ask for credit card info next?

YES! They do!  This is incredible.  Has security and trust been totally forgotten? This is weird.  Does anyone else think this strange?  There is absolutely no indication that gives me peace of mind about how my Credit Card number will be transmitted over the wire to Microsoft.

There is a sentence that says "Provided by arvato digital services, llc," with a link to "privacy statement" and "Imprint".  When I click either link, I am currently taken to a page that says "Internet Explorer cannot disply the webpage".  Wow! This is incredible.  No way on Earth am I going to proceed!

I'm ditching this process for now.  Maybe I can find some other way in.  I was excited, but now I'm just disappointed.