SSIS package does not appear in VS 2010

Question

We use VS 2010 (BIDS), SQL 2012 and TFS. We have a solution with two projects. One for ETL and one for reporting. Recently, the ETL project prompted me to save / merge another version on the project project server .dtproj server. I assume the version number is greater than mine than I want this file. This prompts me to do the same with another project in the solution at the moment. Look at the application. I did not do this, since the last time he screwed my environment! I am SURE that this is 100% my lack of understanding of TFS. That being said, I don’t know what to read / research, to educate myself, not to spoil it again.

When I clicked on the “Take the server version” link, it offered me a dialog box that read something about that:

"The project.dtproj file was modified outside of the original editor ..."

Do you want to:

Save AS Save Cancel Ignore 

I clicked "Save As." Then, when I realized that I would get two DTproj files, one related to the solution, and the other not, I hit.

That's when it all went wrong.

After I hit cancellation and reloaded the project in VS2010, my packages were not visible in the SSIS package folder in VS 2012. They are in TFS (I see them in the source explorer). They are in FS (I see them in Windows Explorer).

However, I am not doing anything to bring them back to the project.

If I try to add an existing package and navigate to it in the file system, I get the file in the project, but it appears as a copy of the file. I see the new file and the original in the file system, and the new file that appears in the project is called "Project (1) .dtsx"

How to return the project to normal operation?

Thanks for any help!

Sean

Answer 1

A .dtproj file is simply XML that defines which files make up the project. Each release has a slightly different format from another, but not particularly complex.

As a rule, I found that “tearing apart” a project file between developers adds a new package to the mix. It seems simple enough, but for some reason, the diff utility cannot come to terms with the differences when adding a package. If I know that there will be several developers working on the SSIS solution, I’d better try creating the placeholder packages first so that we don’t have Dev A adding MyFabulousPackage to the project file while Dev B added OutrageouslyGoodPackage at the same time time. Instead, everyone has the same project file, and then performs his task of correcting the contents of his focus area.

Sample .dtproj

 <?xml version="1.0" encoding="utf-8"?> <Project xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <DeploymentModel>Project</DeploymentModel> <ProductVersion>11.0.2100.60</ProductVersion> <SchemaVersion>9.0.1.0</SchemaVersion> <State>$base64$P...g==</State> <Database> <Name>SSISFoo.database</Name> <FullPath>SSISFoo.database</FullPath> </Database> <DataSources /> <DataSourceViews /> <DeploymentModelSpecificContent> <Manifest> <SSIS:Project SSIS:ProtectionLevel="DontSaveSensitive" xmlns:SSIS="www.microsoft.com/SqlServer/SSIS"> <SSIS:Properties> <SSIS:Property SSIS:Name="ID">{83ded95e-49f0-4781-ab8f-7f8954d6423a}</SSIS:Property> <SSIS:Property SSIS:Name="Name">SSISFoo</SSIS:Property> <SSIS:Property SSIS:Name="VersionMajor">0</SSIS:Property> <SSIS:Property SSIS:Name="VersionMinor">0</SSIS:Property> <SSIS:Property SSIS:Name="VersionBuild">0</SSIS:Property> <SSIS:Property SSIS:Name="VersionComments"> </SSIS:Property> <SSIS:Property SSIS:Name="CreationDate">2013-03-19T10:24:18.8594643-05:00</SSIS:Property> <SSIS:Property SSIS:Name="CreatorName">home\bfellows</SSIS:Property> <SSIS:Property SSIS:Name="CreatorComputerName">Thangorodrim</SSIS:Property> <SSIS:Property SSIS:Name="Description"> </SSIS:Property> <SSIS:Property SSIS:Name="FormatVersion">1</SSIS:Property> </SSIS:Properties> <SSIS:Packages> <SSIS:Package SSIS:Name="Package.dtsx" SSIS:EntryPoint="1" /> </SSIS:Packages> <SSIS:ConnectionManagers /> <SSIS:DeploymentInfo> <SSIS:ProjectConnectionParameters /> <SSIS:PackageInfo> <SSIS:PackageMetaData SSIS:Name="Package.dtsx"> <SSIS:Properties> <SSIS:Property SSIS:Name="ID">{3BEEFDD8-FB86-4804-9049-EB28C4BD69DD}</SSIS:Property> <SSIS:Property SSIS:Name="Name">Package</SSIS:Property> <SSIS:Property SSIS:Name="VersionMajor">1</SSIS:Property> <SSIS:Property SSIS:Name="VersionMinor">0</SSIS:Property> <SSIS:Property SSIS:Name="VersionBuild">1</SSIS:Property> <SSIS:Property SSIS:Name="VersionComments"> </SSIS:Property> <SSIS:Property SSIS:Name="VersionGUID">{3087F645-C4C4-4773-8040-E2DAFFE8B922}</SSIS:Property> <SSIS:Property SSIS:Name="PackageFormatVersion">6</SSIS:Property> <SSIS:Property SSIS:Name="Description"> </SSIS:Property> <SSIS:Property SSIS:Name="ProtectionLevel">0</SSIS:Property> </SSIS:Properties> <SSIS:Parameters /> </SSIS:PackageMetaData> </SSIS:PackageInfo> </SSIS:DeploymentInfo> </SSIS:Project> </Manifest> </DeploymentModelSpecificContent> <Miscellaneous /> <Configurations> <Configuration> <Name>Development</Name> <Options> <OutputPath>bin</OutputPath> <ConnectionMappings /> <ConnectionProviderMappings /> <ConnectionSecurityMappings /> <DatabaseStorageLocations /> <ParameterConfigurationValues /> </Options> </Configuration> </Configurations> </Project> 

What are you experiencing

What you experience with "Package (1) .dtsx" is the bloody annoying and counter intuitive addition of an existing package to the project. When you click "Add Existing Package" and select Package.dtsx in the project folder

• Visual Studio / BIDS / SSDT will try to copy this package to a local folder
• This file already exists and instead of compressing it, it is going to save it with (number) added to it

This makes sense because the window that allows you to select a package allows packages to be in the package repository or SQL Server. Suddenly, if you notice the heading “Add a copy of an existing package” (though I never noticed that the word “Copy to this day and that after 8 years of using the product”)

What are you doing?

Do not add an existing package. Instead, right-click on the project and "Add, Existing Item", which will then become your existing SSIS package.