Browse by Tags
All Tags »
.Net related (
RSS)
I found an interesting comparison of different Version Control Systems: http://better-scm.berlios.de/comparison/comparison.html
But I noticed that Team Foundation Server is missing.
Click the title of this post to see the list with the addition of TFSC and to help to improve it.
...
As confirmed by my friend Raffaele Rialdi (an italian MVP) in this post on his italian blog, also other types of authentication are vulnerable by the %5c or \ characters in the URL. Try to protect a site with Windows Autentication, and then to protect...
From the Installation Roadmap (\docs\default on the VSTS CTP DVD): Note This release only supports a three-computer deployment of Team Foundation, one computer for each logical tier (database, application, and client). Uhm... it's time to acquire some...
Nothing... at least this is the impression by looking at the workspace ... Nobody answers on the MessageBoard, nobody informs us about the status of the bugs... Please let we know something... at least we know what to do. I don't want to fork the main...
At first one year ago they started calling the next .NET Framework 1.2, you can see it in SQL Server Yukon Beta 1, or in the Alpha versions of Whidbey... After a while, they decided to give it the 2.0 version number, considering the huge amount of improvements...
I've released the stable version of URLScanMonitor v1.0.100.0, adding the ability to disable the alert panels. If there aren't other requests, I'll consider the program complete. You can find it here on the GotDotNet Workspace . Here you can find the...
In these days I've written a little tool, in part inspired by Darrel Norton 's great URLScan Watcher . I needed a little pet project to play with VB Power Pack, the FileSystemWatcher and other little things, and considering that I needed also some functionalities...
I've downloaded and installed Windows XP SP2 and everything is ok! I was already using build 2162, so I was prepared, but the update process was very very smooth. Now I remember that some folks from Microsoft promised that right after the SP2 release...
To be notified on the server that the WSE2 client has a Timestamp problem (and perhaps doing something like logging the problem), I used this solution on the client: try { proxyWse.DoSomething(); } catch { try { proxy.LogError(); throw; } catch { throw;...
Regarding my previous post called " I really hate Timestamp check in WSE... " I've discovered (on WSE NGs) how to mitigate the problem. There is an element in the .config file that is used to change the default value (5 minutes): <microsoft.web.services2>...
More Posts
Next page »