multi-project solution - deployment

Hi there, 

There is a solution which has been built by a developer who is no longer with us. 

The solution consists of three projects.

All three projects have been assigned a common .snk key in the signing tab in the properties.

None of the projects has any value in the Application Name box on the Deployment tab. 

It is deployed in our prod system, 

it builds fine, 

it deploys without error but then, 

It is not visible in the BizTalk Administration Console. 

Does anyone knows why ?

June 22nd, 2015 9:17am

There's a few details missing but, if no Application name was specified during import, then the Assemblies, and all other Artifacts, would have been placed in the Default Application which is probably BizTalk Application 1.

Open the <All Artifacts> Application, then Resources. Find this app's Assemblies and check the Application name. That's where they are.

Note, the Application Name in Visual Studio only affects deploying from Visual Studio, this has no effect on any production deployment, or at least it shouldn't since you shouldn't be deploying to Production from VS.

Free Windows Admin Tool Kit Click here and download it now
June 22nd, 2015 9:24am

Tanks, 

So do you think I should just put a value XYZ on the Application Name on the Deployment tab in the Properties of each Project ?

June 22nd, 2015 9:45am

Yes, they should match so your DEV environment matches your PROD setup.
Free Windows Admin Tool Kit Click here and download it now
June 22nd, 2015 10:02am

As been correctly pointed out by boatseller if you do not give application name in Project properties than while deployment than all the BizTalk Application is loaded into default BizTalk Application 1 shipped with BizTalk Admin console.

For Application to work  as per your prod or test environment you need to see application structure on the prod environment and change the project properties Application name as per deployed Application

Thanks

Abhishek

June 22nd, 2015 12:23pm

There's a few details missing but, if no Application name was specified during import, then the Assemblies, and all other Artifacts, would have been placed in the Default Application which is probably BizTalk Application 1.

Open the <All Artifacts> Application, then Resources. Find this app's Assemblies and check the Application name. That's where they are.

Note, the Application Name in Visual Studio only affects deploying from Visual Studio, this has no effect on any production deployment, or at least it shouldn't since you shouldn't be deploying to Production from VS.

Free Windows Admin Tool Kit Click here and download it now
June 22nd, 2015 1:22pm

There's a few details missing but, if no Application name was specified during import, then the Assemblies, and all other Artifacts, would have been placed in the Default Application which is probably BizTalk Application 1.

Open the <All Artifacts> Application, then Resources. Find this app's Assemblies and check the Application name. That's where they are.

Note, the Application Name in Visual Studio only affects deploying from Visual Studio, this has no effect on any production deployment, or at least it shouldn't since you shouldn't be deploying to Production from VS.

June 22nd, 2015 1:22pm

There's a few details missing but, if no Application name was specified during import, then the Assemblies, and all other Artifacts, would have been placed in the Default Application which is probably BizTalk Application 1.

Open the <All Artifacts> Application, then Resources. Find this app's Assemblies and check the Application name. That's where they are.

Note, the Application Name in Visual Studio only affects deploying from Visual Studio, this has no effect on any production deployment, or at least it shouldn't since you shouldn't be deploying to Production from VS.

Free Windows Admin Tool Kit Click here and download it now
June 22nd, 2015 1:22pm

As been correctly pointed out by boatseller if you do not give application name in Project properties than while deployment than all the BizTalk Application is loaded into default BizTalk Application 1 shipped with BizTalk Admin console.

For Application to work  as per your prod or test environment you need to see application structure on the prod environment and change the project properties Application name as per deployed Application

Thanks

Abhishek

June 22nd, 2015 4:21pm

As been correctly pointed out by boatseller if you do not give application name in Project properties than while deployment than all the BizTalk Application is loaded into default BizTalk Application 1 shipped with BizTalk Admin console.

For Application to work  as per your prod or test environment you need to see application structure on the prod environment and change the project properties Application name as per deployed Application

Thanks

Abhishek

Free Windows Admin Tool Kit Click here and download it now
June 22nd, 2015 4:21pm

As been correctly pointed out by boatseller if you do not give application name in Project properties than while deployment than all the BizTalk Application is loaded into default BizTalk Application 1 shipped with BizTalk Admin console.

For Application to work  as per your prod or test environment you need to see application structure on the prod environment and change the project properties Application name as per deployed Application

Thanks

Abhishek

June 22nd, 2015 4:21pm

Error 1 Failed to add resource(s). Change requests failed for some resources. BizTalkAssemblyResourceManager failed to complete end type change request. Assembly "C:\Users\USERNAME\AppData\Local\Temp\BT\PID5144\BizTalkAssembly\14aac4196e532f09141f39d4f881b656\CFLY.StartAssessment.Pipelines.dll" does not appear to be a BizTalk assembly, and cannot be deployed to the Configuration database. If this assembly is referenced by other BizTalk assemblies, it needs to be installed into the global assembly cache (GAC) of each BizTalk server. 0 0

Hi there, 

I am trying to deploy my multiporject solution but it fails.

The folder: C:\Users\USERNAME\AppData\Local\Temp\BT does not exists so I have no idea why would VS be stuck with that. 

The computer has been restarted and thus also the host instance. 

I'm not sure why the error then...

Free Windows Admin Tool Kit Click here and download it now
June 23rd, 2015 5:55am

If this is a different question, you should mark the appropriate Answers here an open a new thread.
June 23rd, 2015 5:34pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics