Convert.ToString();: March 2007

Custom Site Definition, Solution Package, App_GlobalResource & Web.Config

0 Comments
Published by Ciaran McAuliffe on Tuesday, March 6, 2007 at 12:28 PM.

It was hard to come up with a good title for a this post, but this one will do I guess. Solution packages are one of the greatest features in MOSS 2007, and for a while (up until 2 minutes ago) I was kind of anoyed that the solution packages provided no way to modify the Web.config, or to get a *.resx file into the App_GlobalResources folder. Well I just found a way to accomplish these tasks, but it really (kinda) only works if you are creating a site definition that will be deployed before the Web Application is created. Here is how you perform these two tasks:

Modify the Web.config

Have a read of the link below and when you are done modify your solution package to drop of your custom webconfig.*.xml file off in the c:\Program Files\Common Files\Microsoft Shared\web server extensions\12\CONFIG folder

How to: Add Custom Configuration Settings for Extending Virtual Servers

Add a *.resx file to App_GlobalResources folder

Following the lead from the article above, I discovered that you just need to create your *.resx file and get your solution package to drop it off in the c:\Program Files\Common Files\Microsoft Shared\web server extensions\12\CONFIG\Resources folder.

So, when you create a new Web Application the webconfig.*.xml file will be merged with the Web.config file of the site, and the *.resx file will be dropped off in the App_GlobalResources file.

The downsides of this solution are :

The Web.config entries and the *.resx file will be added to all web applications regardless of whether your site definition is being added to it.
This solution will not work for web parts, or features, or anything else really, because the files need to be dropped off before the Web Application is created.
When you remove the solution package from SharePoint the entries are left in the Web.config and the *.resx files are left in the App_GlobalResources.

I think the solution packages should be an extensible framework, in the same way as we have feature handlers, so that you can deploy anything to anywhere and then have it cleaned up when you remove it.

Team Foundation Server Web Services

0 Comments
Published by Ciaran McAuliffe on Thursday, March 1, 2007 at 9:52 PM.

I searched everywhere trying to find a list of the web services that surround TFS, and I only discovered them because I found the url of one web server which had a function that listed all of them. Anyway, just to make it easy for others, here they are:

TFS Web Services
/Services/v1.0/AuthorizationService.asmx
/Services/v1.0/CommonStructureService.asmx
/Services/v1.0/EventService.asmx
/Services/v1.0/GroupSecurityService.asmx
/Services/v1.0/ProjectMaintenance.asmx
/Services/v1.0/ProcessTemplate.asmx
/Services/v1.0/Registration.asmx
/Services/v1.0/ServerStatus.asmx

/Warehouse/v1.0/WarehouseController.asmx
/Warehouse/v1.0/WarehouseController.asmx

/Build/v1.0/BuildStore.asmx
/Build/v1.0/BuildController.asmx
/Build/v1.0/Integration.asmx
/Build/v1.0/Integration.asmx
/Build/v1.0/Integration.asmx
/Build/v1.0/PublishTestResultsBuildService.asmx

/WorkItemTracking/v1.0/ClientService.asmx
/WorkItemTracking/v1.0/ConfigurationSettingsService.asmx
/WorkItemTracking/v1.0/Integration.asmx
/WorkItemTracking/v1.0/Integration.asmx
/WorkItemTracking/v1.0/Integration.asmx
/WorkItemTracking/v1.0/Integration.asmx

/VersionControl/v1.0/repository.asmx
/VersionControl/v1.0/administration.asmx
/VersionControl/v1.0/integration.asmx
/VersionControl/v1.0/integration.asmx
/VersionControl/v1.0/integration.asmx
/VersionControl/v1.0/item.asmx
/VersionControl/v1.0/upload.asmx

/Build/v1.0/PublishTestResultsBuildService.asmx
/Build/v1.0/PublishTestResultsBuildService.asmx

Reporting Services Web Services
https://[report_server_url]/ReportServer/ReportService.asmx

Convert.ToString();

Custom Site Definition, Solution Package, App_GlobalResource & Web.Config

Team Foundation Server Web Services

Archives