Thursday, 31 August 2006

Security Engineering

Just picked this up on Schneier's blog. You can now download Security Engineering free and legal.

It's a great book, go get it!

Posted by kevin at 2:29 PM in General

Responses (0)

Wednesday, 23 August 2006

ASP.Net Web Project Details

I've been asked this on a course several times so I thought I'd mention it here. By default ASP.Net 2.0 web projects don't have a project file, but project specific information has to be kept somewhere. That somewhere is in C:\documents and settings\[user name]\Local Settings\Application Data\Microsoft\WebsiteCache

Thanks to Simon Horrell and Brock for getting to the bottom of this.

Posted by kevin at 9:09 AM in Net

Responses (0)

Monday, 21 August 2006

SpeedTest

This is very cool

speedtest.net

Posted by kevin at 1:29 PM in General

Responses (0)

Wednesday, 9 August 2006

TestResults "In" Directory

When unit testing in VSTS I always puzzled as to how the "In" TestResults sub-directory was used, the "Out" directory is obvious. Turns out that it is used for two things. Firstly the code coverage results are stored there. Secondly it is used as the location of files used as part of the test that aren't copied to the output directory. Files can be put into the "In" directory by calling TestContext.AddResultFile("filename"); You could use this to, for example, store files that were created and/or written to as part of the testing process.

Thanks to Michael Koltachev for pointing this out on the VSTS forums.

Posted by kevin at 10:09 AM in Net

Responses (0)

Sunday, 6 August 2006

Access is denied. in VSTS Team Build

A wise man once said "A man who never made a mistake, never made anything", well I've just made a fundamental error and learned a lot from it.

I've been using Team Build to build projects and recently kept getting "Access is denied." on files in either a project's obj directory or in the bin directory. This didn't happen for all the projects within a solution, just one or two. Checking the security within the build server showed that all the directories for all the projects had the same security settings. It took me a while to figure out what was happening!

Some time during the lifetime of the project Visual Studio had crashed . I had some projects that were in the solution but had not been added to source control correctly. To fix this I went through and added the folders containing the projects to source control, then checked everything in. This was the mistake. When I added the folder it also meant I added the binary files, i.e. the files in the obj and bin folders. During a build the buildserver checks out the files defined in the workspace mappings, including the binaries that I had now added. These files are checked out as read-only. Of course, when the project was built, as the binaries were read-only they could not over-written so the build was failing.

Deleting the binaries from source control fixed the problem. And the moral of the story is, don't put anything into source control that wil be re-built as part of the standard project build!

Posted by kevin at 11:10 AM in Net

Responses (0)

« August »
SunMonTueWedThuFriSat
  12345
6789101112
13141516171819
20212223242526
2728293031