Technical problems in using GAT for our reference implementation

Topics: July and December Releases Forum
Apr 5, 2007 at 4:23 PM
Some of the problems faced by the team are listed here.

1. If we are creating a new guidance package, and we have our solution template in place. We may be having a number of custom assemblies w. r. t to the solution. We can refer different assemblies in the csharp project file.
We are placing the common assemblies in a common folder. How can we specify the relative path of these assemblies in the project file?

2. How can we refer different assemblies if a project is of type Web Project

3. Is there any way to create web folder on the target machine’s IIS. We have three web projects that need to be hosted in IIS. We want to host these projects in IIS when the solution is unfolded from the guidance package

Problems Faced:
1. We want to leverage the functionality of Web Client Software Factory and Web Service Software Factory in my custom guidance package. If We are going to refer their respective dlls, we also need to take the Microsoft.Practices.RecipeFramework.Extensions reference as well. Unfortunately, each of the above software factory have their respective Microsoft.Practices.RecipeFramework.Extensions with the same signatures, and we can take only one reference of this dll which will allow us to either use the Web Client Software Factory or Web Service Software Factory.

Observations:
The Microsoft.Practices.RecipeFramework.Extensions of Web Client Software Factory contains all the classes which are also available in the Microsoft.Practices.RecipeFramework.Extensions dll provided with Web Service Software Factory. We think that the Microsoft.Practices.RecipeFramework.Extensions project should be made separate from the different factories so that people who want to leverage the functionality of the Microsoft.Practices.RecipeFramework.Extensions can do that without any hassle.

2. We have created a new guidance package, which contains a setup project that is used to run setup for it. The whole solution builds successfully. When we run the setup some times the setup runs perfectly and installs the guidance package and some times it is stuck at the end and does not respond. If we cancel the setup there is no response. We go and look into add remove programs, it doesn’t show up as installed. If we run the setup again, it says that the guidance package is already installed. When we logoff and login again, we can see the installed package in the add remove programs. If we try to create a new application based on this template from visual studio, it is not created. If we try to uninstall the package, it gives error.

We have also mentioned these issues during our software factories discussions with Jack Greenfield. Please help us out.
Developer
Apr 6, 2007 at 6:15 PM
Problems faced answers:
  1. You can get the already public released GAX Extension Library and use it as a common binary between WCSF and WSSF. (This library will be also used in WSSF V3).
  2. Perhaps you can post this issue to the GAX\GAT Forums or check if there is any known issue about this. You may also verify that you are not including in the "Detected Dependencies" any system/VS library that might be causing troubles if you tray to overwirte it or remove it (tipically are; EncDTE,EnvDTE80, Interop.Shell32, GAX bits and any other Visual Studio library.

Charly