.Net ramblings
# Sunday, 19 September 2004
Problems using Visual Studio.Net and Visual Source Safe with Web Projects

If you get annoyed at Visual Source Safe's complications with using asp.net web projects, and integrating them with Visual Studio.Net, an increasingly popular approach is to use 'class library' projects instead of web projects.  (Of course, this problem will disappear with Whidbey but i'm still using VS 2003).  A web project compiles a dll / class library anyway, and VS doesn't have to interact with IIS to load the project.  It isn't hard to set up but it does require careful instructions to be followed.  A guy called Fritz Onion prepared the content below:

This is copied/pasted here in case Fritz's link changes or disappears. The original content is available from:

Reference prepared by Fritz Onion

The Web Project wizard in Visual Studio .NET is convenient for creating quick ASP.NET applications on your local machine, but in an effort to simplify your life, it also makes many decisions for you that are difficult to change if you need more flexibility. My biggest pet peeve with Web Projects is that you cannot even open a .sln file if the virtual directory mapping in IIS is not set up correctly. I also dislike the way it places .sln and .csproj | .vbproj files in a separate location from the actual source files (I understand that this is necessary to allow application creation directly on a server, but I never deploy that way).

As a result, most of my web projects are created as standard class library projects. Unfortunately this means that you don't get the nice Web component wizards (like WebForms and UserControls). However, with a little tweaking, you can have it all.  I have prepared this document describing how to enable these wizards in class library projects (thanks to Dan Sullivan for pointing out how to do this), as well as how to convert existing Web Projects to class library projects and still keep the nice integrated debugging.

To enable Web wizards in a class library project:

In a directory called

C:\Program Files\Microsoft Visual Studio .NET 2003\VC#\CSharpProjectItems\LocalProjectItems

is a file callled localprojectitems.vsdir.

Likewise in a directory

C:\Program Files\Microsoft Visual Studio .NET 2003\VC#\CSharpProjectItems\WebProjectItems

is a file called webprojectitems.vsdir.

If open the second file with notepad you can figure out the lines to copy to the first file to be able to add the usual files you need to create an aspx page or web service to a class lib project.

Once you have copied these thing open VS, open a class lib and go to add new item and you will see these additional file types available.

To set the output of a class library project to go to a /bin directory of your choosing:

1. Right-click on the project and select properties
2. Set Configuration to 'All Configurations' to affect both debug and release builds
3. Under configuration properties/build set the OutputPath to the /bin directory

To convert an existing web project into a class library project:

1. Open the .sln file in a text editor, and change the reference to the project from an http://... reference to a simple reference to the .csproj (or .vbproj) filename. For example:
Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "WebApplication133", "http://localhost/WebApplication133/WebApplication133.csproj", "{39CB37A5-F735-4684-B5DA-DD355B683090}"

Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "WebApplication133", "WebApplication133.csproj", "{39CB37A5-F735-4684-B5DA-DD355B683090}"

2. If there is one, delete the .webinfo file
3. Open the .csproj (or .vbproj) file and change the ProjectType attribute from "Web" to "Local"

To set up a class library project to run a browser when you debug it:

1. Right-click on the project in the solution explorer and select properties
2. Under Configuration Properties/Debugging, change Debug Mode from 'Project' to 'URL'
3. Hit Apply
4. In the Start URL field, enter the complete url to the page you want to hit to debug, like:

Sunday, 19 September 2004 23:32:44 (GMT Daylight Time, UTC+01:00)  #    Comments [0]  .Net General

# Tuesday, 14 September 2004
A sample NTbackup script, with the current date/time in the filename and backup label

This script is based on the FAQ on http://www.jsiinc.com/SUBE/tip2200/rh2265.htm.

If you ever tried to automate NTbackup, you probably got it up and running, scheduled every day or week, but then noticed over time that the date and time labels that go on the backup file are the current date/time of when you created the backup set.  This useful shell script provides a more intelligent solution by parsing the current date and time and inserting them into the filename and backup label.  This makes the backups much easier to identify in the case where you need to restore some files.

The script below makes a full backup (not differential) of the files specified in the backup set.bks. It doesn't verify the backup, and lastly it sends a copy of the backup file to another computer (just in case), that's what the last 3 lines are for.  You can obviously remove this step if you don't want it.

If you don't fully understand all the parameters of the NTbackup.exe... command, it's explained well here.

Save the following text as a .cmd file and add it is a scheduled task in Windows.

@for /f "Tokens=1-4 Delims=/ " %%i in ('date /t') do  @set dt=%%i-%%j-%%k-%%l
@for /f "Tokens=1" %%i in ('time /t') do @set tm=-%%i
@set tm=%tm::=-%
@set dtt=%dt%%tm%
@echo Copying backup set: %dtt%.
@echo Please wait...
@C:\WINDOWS\system32\ntbackup.exe backup "C:\Documents and Settings\Administrator\Local Settings\Application Data\Microsoft\Windows NT\NTBackup\data\backup set.bks" /a /d "Backup %dtt%" /v:no /r:no /rs:no /hc:off /m normal /j "%dtt%" /l:s /f "G:\Auto Backups\Backup %dtt%.bkf"

@echo Sending backup file to Server2. Please wait...
@xcopy "@G:\Auto Backups\Backup %dtt%.bkf" "@\\Server2\Backup_Copy" /Y
@echo Finished.

Tuesday, 14 September 2004 11:18:09 (GMT Daylight Time, UTC+01:00)  #    Comments [17]  Windows Server

# Friday, 10 September 2004
How to turn off Windows auto-expand (and search) for compressed folders

I have a lot of .zip files floating around my computer and Windows XP/2003 includes them with regular folders when browsing in Explorer.  Also, when you search for files, Windows searches inside .zip files which can take a long time because they need to be uncompressed every time to be searched. 

I personally don't want this feature, and after a bit of looking around, i came across a simple solution.  Just unregister the component that does the searching within compressed folders.  Note: this doesn't stop you opening compressed folders, it just means they don't get included in the Windows Explorer tree-view, and they don't get included in searching with the Indexing Service.

Run the following command (Start > Run) or you can put it in the Run section of the Windows Registry in case Windows automatically adds back the zip dll.

regsvr32 /u C:\windows\system32\zipfldr.dll 

If you go need to put it back again, then run:

regsvr32 C:\windows\system32\zipfldr.dll 

Many thanks to 'SJB' for his/her post on http://www.annoyances.org/exec/forum/winxp/1054284272

Friday, 10 September 2004 22:36:46 (GMT Daylight Time, UTC+01:00)  #    Comments [0]  Windows Server

# Thursday, 29 July 2004
Controlling a dial-up connection via a web service


I just finished writing a simple client/server .Net application that allows windows PCs on a LAN to control the dial-up connection on a web server. 
I'm currently using it at home on a small ad-hoc wireless network because the windows Internet Connection Sharing setting for 'dial on-demand' is very unreliable and it dials up when you don't want it to.  This way you control when it connects and disconnects. Also, i was using terminal services to connect and disconnect which is way overkill!

I have put the source code and executables online for anyone to download, use modify etc. Download: RemoteDialer.zip (94 k).  There is a readme file in there, but here are the instructions anyway which explain how it works and how to set it up.

How it works

The web server has methods for Dial() and Hangup().  They each call a batch file with Process.Start, which is configured to output the result of the operation to a text file.  The batch files use the rasdial.exe tool to connect and disconnect the connection. The web service reads the text file before sending back the contents of it, to the client that requested the operation.

The desktop application for client PCs has a system tray icon, with a right-click menu to Start or Stop the connection.

There is also a web page to connect/disconnect, so you can allow non-windows users (who obviously couldn't run the desktop app) who are on your network to control the connection. To go to this page, just go to the address of the v.dir on the server.


To configure the web server:

 - set up a new application pool which runs as Local Service
 - copy the 'Web' folder to the web server
 - make it a virtual directory
 - set the AppPool for the v.dir to the appPool you just created
 - Copy the 2 batch files in the 'Batch Files' folder to the server.
 - It's easiest to put them in the c:\ root, otherwise you can
   update the web.config application keys accordingly.

To configure the windows PCs:

 - Locate the RemoteDialer.exe.config file in \WinClient\bin
 - Adjust the http value key to match the server and v.dir name on the
 - Copy the WinClient\Bin folder to each PC
 - Run the .exe and you will see a new icon the system tray.
 - Right-click the tray icon to start or stop the dial up connection
 - The status of the operation is outputted to a pop up box.

Note: The reason for the new Application Pool is so that the web service
can interact with the system and write the output of operations
to text files.


If you have any comments or queries on it, or if there are bugs or problems, email me.  tim@mackeyNO_SPAM_PLEASE.ie

Thursday, 29 July 2004 11:29:17 (GMT Daylight Time, UTC+01:00)  #    Comments [4]  .Net General

# Monday, 26 July 2004
A great ASP.NET treeview control that is compatible with other browsers

I'm building a web front-end for my content management system (so that i can sell it to clients who don't run 100% windows PCs).  and i needed a cross-platform treeview control.  i did a quick search and noticed that the CrapStuff Treeview listed on asp.net was a popular one (http://crapstuff.craponne.org).  Ignoring the unusual name i tried it out and am delighted with it.  i have used the microsoft.ui.webcontrols treeview before and found it frustrating on several issues, that others have also encountered and have remained unresolved due to MS not supporting the control.

programatically the CrapStuff Treeview is great to work with, and i like the DHTML support also so that the control can be expanded fully without any postbacks, unless you want them to happen.

the author's name is Pascal Craponne so that's where he gets the name i suppose.  it's a great control and he has given it out for free.  thank you Pascal!

Monday, 26 July 2004 23:05:05 (GMT Daylight Time, UTC+01:00)  #    Comments [1]  Asp.Net

# Friday, 23 July 2004
Outlook 2003 blocking attachments, kb fix didn't work

someone sent me a .mdb attachment today and i couldn't open it in outlook. no amount of searching the options could change this behaviour. i searched online and found a few microsoft kb articles about it, and how to change the registry to add exemptions to the 'Level 1' list of file extensions, which outlook regards as unsafe.  i did all the steps in the article but it still didn't work.  then i found this GREAT outlook plug in which adds a tab to the outlook options and allows you to configure how outlook handles all the attachments.


How on earth MS forgot about this is beyond me.  they actually suggest that you ask the person who sent it to rename the file with a bogus extension and resend the attachment.  surely it is sufficient to force users to save the file to disk and then open it themselves by choice.  sheesh!

Friday, 23 July 2004 17:51:56 (GMT Daylight Time, UTC+01:00)  #    Comments [0]  General

# Wednesday, 21 July 2004
Some issues with PureComponents Navigator control 2.0

I have built a content management system in windows forms, and i set it up with individual forms to manage each of the aspects to the system. one to manage users, another for templates etc.  however this made the user interface quite cluttered sometimes with several windows open.  so i decided to make my app work like outlook 2003 with its nice control on the left with buttons and side panels on the left, and the main panel on the right for whichever button is selected. 

i chose the pure components navigator control (2.0) and i'm testing it at the moment.  i don't like the way the developers don't give a public support forum, they say it shouldn't need support, but i have had several issues with it.

the main problem i have is that the control seems to crash Visual Studio (2003 enterprise edition) when i add panels to each group and set properties such as anchoring in the designer.  i ended up cutting the code to set up the panels from InitialiseComponent and pasting it into a separate function that i call in the constructor.

also, the group class is supposed to have a FitPanel() method, but it doesn't fill the panel to the size of the space in the control between the buttons.  i tried setting the panel to DockStyle.Fill and it fills the entire control on top of all the other buttons.  I ended up manually creating the panels (right click a group and Add Panel) and then resize it to the desired dimensions, and set the anchor to top|left|bottom|right.  i must say it was quite messy though. 

it seems like a great control and it works quick enough too. i'll need to do more testing before i pay for the license though.

Wednesday, 21 July 2004 23:58:51 (GMT Daylight Time, UTC+01:00)  #    Comments [2]  .Net Windows Forms

# Monday, 12 July 2004
System tray icons in Windows forms apps

If you add a NotifyIcon (system tray icon) to a Windows forms application, you will need to modify the dispose event of the form containing the icon, to explicitly call dispose on the notifyIcon as follows:

protected override void Dispose( bool disposing )
 if( disposing )
  if (components != null)
 base.Dispose( disposing );

if you don't do this, the icon will get left in the system tray after the application quits, until you move the mouse over the icon and then it will disappear.

Monday, 12 July 2004 10:02:42 (GMT Daylight Time, UTC+01:00)  #    Comments [0]  .Net Windows Forms

# Thursday, 24 June 2004
Http Status 400 trying to send large DIME attachments

Testing out my new DIME attachment code with WSE2, i ran into http errors with large uploads.  The error i got was a System.Net.WebException saying that it was a bad request, Http status 400, with an event in the application log under WSE:

HTTP/ASMX Message Receive Failure: Microsoft.Web.Services2.Dime.DimeFormatException: WSE352: The size of the record uuid:c0c3c949-5fb1-4171-88aa-06ce14499e44 exceed its limit.
at Microsoft.Web.Services2.Dime.DimeRecord.UpdateTotalBytesRead...

I had the maxRequestLength set to 128000 in web.config, but i found out that this does not apply to WSE2.  adding the following entry into web.config solved the problem.

<?xml version="1.0" encoding="utf-8" ?>
    <maxRequestLength>256000</maxRequestLength><!-- 256 mb -->

Thursday, 24 June 2004 09:49:24 (GMT Daylight Time, UTC+01:00)  #    Comments [8]  Asp.Net

# Wednesday, 23 June 2004
WSE 2.0 send DIME attachments from client TO a web service

I wanted to improve the performance of my winforms app sending binary data to a web service, so i chose to upgrade to WSE 2.0 and use the DIME specification. 

I checked out the examples in the docs, but only found one with a web service sending an attachment to a client.  i wanted it the other way around.  i tried to modify it to suit my own needs, but couldn't get it to work. (in the end i had the response and request contexts mixed up). I searched high and low online and finally found that there is a sample as part of the WSE full installation which contains just what i wanted.  I could find no mention of this sample in the docs, so I am posting it here.

The code below shows the important methods, on the client and on the server.  It assumes a web project and winforms project both set up for WSE2.0. 

// this is part of a winforms application with an openfiledialog
private void btnUpload_Click(object sender, System.EventArgs e)
  if(this.openFileDialog1.ShowDialog() == DialogResult.OK)
    DimeAttachment dimeAttach = new DimeAttachment("image/gif", TypeFormat.MediaType,this.openFileDialog1.FileName);
    ws = new TestService.Test();
    MessageBox.Show("Upload successful");
    MessageBox.Show("No file selected");

// web service method...
public void ReceiveImage(string filename)
  // Reject any requests which are not valid SOAP requests
  if (RequestSoapContext.Current == null)
    throw new ApplicationException("Only SOAP requests are permitted.");
  if (RequestSoapContext.Current.Attachments.Count == 0)
    throw new ApplicationException("No attachments were sent with the message.");

    FileStream f = System.IO.File.OpenWrite(Server.MapPath("Upload/" + filename));
    Stream s = RequestSoapContext.Current.Attachments[0].Stream;
    byte[] bytes = new byte[s.Length];
    s.Read(bytes, 0, bytes.Length);
    f.Write(bytes, 0, bytes.Length);
  catch(Exception ex)
    throw ex; // or log it...

Wednesday, 23 June 2004 13:08:19 (GMT Daylight Time, UTC+01:00)  #    Comments [1]  .Net General