I am reverse engineering a BizTalk application that has been created by a developer that is no longer with us. 

1. What baffles me is why are his projects not configured with an Application Name in the properties of the project ?

2. What was in your opinion the deployment method ? 

3. What do I do to successfully deploy this and have a similar view in BizTalk Administration Console ? (I can see the pipelines, schemas etc. but just one application although in VS there is one solution and 10 projects.)

4. Additionally; The solution name is T*.Common.BizTalk and the resulting application name is CFLY.Common.BizTalk. Why would that be ?

Developer was mentioning "passenger" but I'm not sure what he meant by that. 

If the developer was part of a release management process, it is very likely there was a build/release management team/tool that built the project and then deployed into T & D or SIT/UAT etc. Tis is why the projects do not have any application name in them.

There can be any number of BizTalk Projects in a VS Solution and all may be targeted to different applications or to the same application and this depends on various factors/established practices, etc.

As a developer I may deploy BizTalk Artifacts into a common application and expect the TFS Build/Release Management process to ensure that the binaries are published as proper installables for consumption into other environments.

Regards.

1. Do you mean the deployment was done using TFS ?

2. What do I do to deploy it without that ? (add the Application Name manually to each project in the solution ???)

1. You would have to fond out that since you're in the account. Need not be TFS, it could be BTDF or a local variant of MSI, etc, etc.

2. Yes. (If those applications do not exist then VS while publishing would create them.)

Regards.

Hi,

1. What baffles me is why are his projects not configured with an Application Name in the properties of the project ?

Check if there is deployment framework (BTDF) in the solution. If that is the case, Application Name is managed by Deployment.btdfproj file. 

2. What was in your opinion the deployment method ? 

If it is not a TFS auto build/ReleaseManagement, BTDF could be it.

3. What do I do to successfully deploy this and have a similar view in BizTalk Administration Console ? (I can see the pipelines, schemas etc. but just one application although in VS there is one solution and 10 projects.)

Two solutions after the solution is successfully built

a. Right click on solution and deploy, this implies the artifacts will be part of "BizTalk Application 1" application in Biztalk Admin console

b. Look for BTDF addin and click the second button (->) which deploys the solution to admin console based on the btdf configuration file

4. Additionally; The solution name is T*.Common.BizTalk and the resulting application name is CFLY.Common.BizTalk. Why would that be ?

BTDF configuration file can mask the Solution name during deployment.

Regards

K

Hi,

The deployment application name is not stored in Project or Solution files, it's stored in BizTalk Project user files (*.btproj.user). It's absolutely normal that the application name appears as empty if you open the solution.

If you want to deploy directly from Visual Studio, you need to set manually the application name in the Deployment tab of each BizTalk Project.

Regards.

1. What baffles me is why are his projects not configured with an Application Name in the properties of the project ?

The Application Name property you see on the Deployment tab is the BizTalk Administrator Application Visual Studio will deploy that project into.

• It is purely a local, login specific setting (stored in the user settings file).
• It is not in source control and not shared by multiple developers.
• It is used only by Visual Studio.
• It has no effect on any other deployment method, .msi, BTDF, Add Resource, etc.
• It is always blank in a new instance of Visual Studio so what you are seeing is perfectly normal.

2. What was in your opinion the deployment method ? 

If this is a follow up on question #1, then there really is no opinion, that is how you Deploy from Visual Studio for DEV time activities.  This is not a PROD level Deployment option.

3. What do I do to successfully deploy this and have a similar view in BizTalk Administration Console ? (I can see the pipelines, schemas etc. but just one application although in VS there is one solution and 10 projects.)

Since that Property represents the BizTalk Administrator Application container, all related projects should have the same value.

4. Additionally; The solution name is T*.Common.BizTalk and the resulting application name is CFLY.Common.BizTalk. Why would that be ?

The Application Name and any Assembly Name, Type Name, Namespace Name etc. are completely unrelated and have no influence on each other.  You can set any of those to anything you want any time.

• Edited by Johns-305 [boatseller]MVP, Moderator 19 hours 37 minutes ago

Any good STEP-BY-STEP tutorial for BTDF ?

Try the BTDF Home Page for documentation, etc. and for a walkthrough refer https://masteringbiztalkserver.wordpress.com/2013/02/05/btd/

Regards.

If any specific issues with BTDF or Deployment, please open a new thread.

1. What baffles me is why are his projects not configured with an Application Name in the properties of the project ?

The Application Name property you see on the Deployment tab is the BizTalk Administrator Application Visual Studio will deploy that project into.

• It is purely a local, login specific setting (stored in the user settings file).
• It is not in source control and not shared by multiple developers.
• It is used only by Visual Studio.
• It has no effect on any other deployment method, .msi, BTDF, Add Resource, etc.
• It is always blank in a new instance of Visual Studio so what you are seeing is perfectly normal.

2. What was in your opinion the deployment method ? 

If this is a follow up on question #1, then there really is no opinion, that is how you Deploy from Visual Studio for DEV time activities.  This is not a PROD level Deployment option.

3. What do I do to successfully deploy this and have a similar view in BizTalk Administration Console ? (I can see the pipelines, schemas etc. but just one application although in VS there is one solution and 10 projects.)

Since that Property represents the BizTalk Administrator Application container, all related projects should have the same value.

4. Additionally; The solution name is T*.Common.BizTalk and the resulting application name is CFLY.Common.BizTalk. Why would that be ?

The Application Name and any Assembly Name, Type Name, Namespace Name etc. are completely unrelated and have no influence on each other.  You can set any of those to anything you want any time.

• Edited by Johns-305 [boatseller]MVP, Moderator Wednesday, July 29, 2015 11:27 AM

1. What baffles me is why are his projects not configured with an Application Name in the properties of the project ?

The Application Name property you see on the Deployment tab is the BizTalk Administrator Application Visual Studio will deploy that project into.

• It is purely a local, login specific setting (stored in the user settings file).
• It is not in source control and not shared by multiple developers.
• It is used only by Visual Studio.
• It has no effect on any other deployment method, .msi, BTDF, Add Resource, etc.
• It is always blank in a new instance of Visual Studio so what you are seeing is perfectly normal.

2. What was in your opinion the deployment method ? 

If this is a follow up on question #1, then there really is no opinion, that is how you Deploy from Visual Studio for DEV time activities.  This is not a PROD level Deployment option.

3. What do I do to successfully deploy this and have a similar view in BizTalk Administration Console ? (I can see the pipelines, schemas etc. but just one application although in VS there is one solution and 10 projects.)

Since that Property represents the BizTalk Administrator Application container, all related projects should have the same value.

4. Additionally; The solution name is T*.Common.BizTalk and the resulting application name is CFLY.Common.BizTalk. Why would that be ?

The Application Name and any Assembly Name, Type Name, Namespace Name etc. are completely unrelated and have no influence on each other.  You can set any of those to anything you want any time.

• Edited by Johns-305 [boatseller]MVP, Moderator Wednesday, July 29, 2015 11:27 AM

1. What baffles me is why are his projects not configured with an Application Name in the properties of the project ?

The Application Name property you see on the Deployment tab is the BizTalk Administrator Application Visual Studio will deploy that project into.

• It is purely a local, login specific setting (stored in the user settings file).
• It is not in source control and not shared by multiple developers.
• It is used only by Visual Studio.
• It has no effect on any other deployment method, .msi, BTDF, Add Resource, etc.
• It is always blank in a new instance of Visual Studio so what you are seeing is perfectly normal.

2. What was in your opinion the deployment method ? 

If this is a follow up on question #1, then there really is no opinion, that is how you Deploy from Visual Studio for DEV time activities.  This is not a PROD level Deployment option.

3. What do I do to successfully deploy this and have a similar view in BizTalk Administration Console ? (I can see the pipelines, schemas etc. but just one application although in VS there is one solution and 10 projects.)

Since that Property represents the BizTalk Administrator Application container, all related projects should have the same value.

4. Additionally; The solution name is T*.Common.BizTalk and the resulting application name is CFLY.Common.BizTalk. Why would that be ?

The Application Name and any Assembly Name, Type Name, Namespace Name etc. are completely unrelated and have no influence on each other.  You can set any of those to anything you want any time.

• Edited by Johns-305 [boatseller]MVP, Moderator Wednesday, July 29, 2015 11:27 AM

1. What baffles me is why are his projects not configured with an Application Name in the properties of the project ?

The Application Name property you see on the Deployment tab is the BizTalk Administrator Application Visual Studio will deploy that project into.

• It is purely a local, login specific setting (stored in the user settings file).
• It is not in source control and not shared by multiple developers.
• It is used only by Visual Studio.
• It has no effect on any other deployment method, .msi, BTDF, Add Resource, etc.
• It is always blank in a new instance of Visual Studio so what you are seeing is perfectly normal.

2. What was in your opinion the deployment method ? 

If this is a follow up on question #1, then there really is no opinion, that is how you Deploy from Visual Studio for DEV time activities.  This is not a PROD level Deployment option.

3. What do I do to successfully deploy this and have a similar view in BizTalk Administration Console ? (I can see the pipelines, schemas etc. but just one application although in VS there is one solution and 10 projects.)

Since that Property represents the BizTalk Administrator Application container, all related projects should have the same value.

4. Additionally; The solution name is T*.Common.BizTalk and the resulting application name is CFLY.Common.BizTalk. Why would that be ?

The Application Name and any Assembly Name, Type Name, Namespace Name etc. are completely unrelated and have no influence on each other.  You can set any of those to anything you want any time.

• Edited by Johns-305 [boatseller]MVP, Moderator Wednesday, July 29, 2015 11:27 AM

1. What baffles me is why are his projects not configured with an Application Name in the properties of the project ?

The Application Name property you see on the Deployment tab is the BizTalk Administrator Application Visual Studio will deploy that project into.

• It is purely a local, login specific setting (stored in the user settings file).
• It is not in source control and not shared by multiple developers.
• It is used only by Visual Studio.
• It has no effect on any other deployment method, .msi, BTDF, Add Resource, etc.
• It is always blank in a new instance of Visual Studio so what you are seeing is perfectly normal.

2. What was in your opinion the deployment method ? 

If this is a follow up on question #1, then there really is no opinion, that is how you Deploy from Visual Studio for DEV time activities.  This is not a PROD level Deployment option.

3. What do I do to successfully deploy this and have a similar view in BizTalk Administration Console ? (I can see the pipelines, schemas etc. but just one application although in VS there is one solution and 10 projects.)

Since that Property represents the BizTalk Administrator Application container, all related projects should have the same value.

4. Additionally; The solution name is T*.Common.BizTalk and the resulting application name is CFLY.Common.BizTalk. Why would that be ?

The Application Name and any Assembly Name, Type Name, Namespace Name etc. are completely unrelated and have no influence on each other.  You can set any of those to anything you want any time.

• Edited by Johns-305 [boatseller]MVP, Moderator Wednesday, July 29, 2015 11:27 AM