Visual Studio Team System 2005 Profiler does not support IE8
Apparently if you try to pr ofile a ASP.NET web project using VSTS 2005 Developer Edition, and you are using IE8, the profiler can’t launch the website (pic above), then VS2005 will gives you the follow error “Performance report XXX contains no data” (pic below). At the moment, the only way is to run it in a host or VM with IE7 installed.
TFS 2008 – Project deleted but SharePoint side failed to be deleted
I tried to use TFSDeleteProject command to remove the project from the TFS server,
tfsdeleteproject /server:myserver myprojectname
but at the end of the process there is this error message
Deleting from Build …
Done
Deleting from Work Item Tracking …
Done
Deleting from Version Control …
Done
Deleting Report Server files …
Done
Deleting SharePoint site …
Could not connect to ‘http://TFS08:17012/_vti_adm/admin.asmx’
The request failed with the error message:
–
<html><head><title>Object moved</title></head><body>
<h2>Object moved to <a href="http://tfs08:17012/_layouts/1033/error.aspx?ErrorTe
xt=Request%20timed%20out%2E">here</a>.</h2>
</body></html>
Then I tried to repeat the command again with the /force option (tfsdeleteproject /force /server:myserver myprojectname), I still get the error
Deleting from Build …
Done
Deleting from Work Item Tracking …
Done
Deleting from Version Control …
Not found
Deleting Report Server files …
Not found
Deleting SharePoint site …
Exception of type ‘Microsoft.SharePoint.SoapServer.SoapServerException’ was thro
wn.
Deleting from Team Foundation Core …
Done
But actually what happened is everything within TFS have been safely removed except the SharePoint, so you need to go into SQL Server Management Studio and connect to WSS_Config database
Select Id From Sitemap Where Path = ‘/Sites/myprojectname’
Grab the Id and execute this SQL
exec dbo.proc_dropSiteMap @Id=%Id%
After that you still need to clean up your WSS_Content database by executing this
exec proc_DeleteSite %Id%
But do note you might have nothing to delete in the WSS_Content
Slides and documents on Devtalk 10 Apr 09
Go here to download the files
SharePoint innovations in Visual Studio 2010
Today there is no build in support for SharePoint found inside Visual Studio 2008 except the SharePoint workflow project. If you want to create studd like Site Definition etc. you need to download the Windows SharePoint Services 3.0 Tools for Visual Studio. It is available for VS2005 as well as VS2008. So in TechEd EMEA 2008, Microsoft announced that Visual Studio 2010 tools for SharePoint will be build in for VS2010.
Channel 9 did an interview with Reza Chrisaz on what are the new features in VS2010 for SharePoint developers. You can download the video here. I list down some of Reza’s Key callouts
SharePoint project templates build-in for VS2010
At last!! Visual designer for SharePoint webparts!!
Exploring SharePoint artifacts inside Server Explorer
Package Explorer – sort of like the one we have with VseWSS today
One of my favourite feature – the feature explorer
Adding Solution to TFS source control with Team Build and nightly build support
How to deploy a WCF web service project onto IIS6/7
In your webservice project, you have PrecompiledWeb folder, this folder contain the web service project in compiled form. Copy the content of the PrecompiledWeb, which is the CustomXmlService folder in this case to c:\inetpub\wwwroot
Now the folder is a website in the web server (but without the ability to run .NET code) so go to your IIS manager console to make this website to a web application. In the console you will see that you newly copied folder does not have a globe icon.
You can see the website in your Default Web Site, in IIS7 right click and select Convert to Application.
Still inside IIS7, a new window will pops up, click OK to accept the settings.
For IIS6 right click to open up the property page of the website
A new window will pops up, showing the default Directory tab
What you need to do is to click on the Create button on the lower half of the window
Click OK if you are not changing the application pool or execute permissions. Leave the permission at Scripts only.
To test out the web service, open it inside browser and the service description will come out.
In Visual Studio client project, delete your project Service Reference and add a new one pointing to this deployed web site.
