NEXT DESIGN

Popularity: 12% [?]

Built-in caching that Visual Studio 2008 (or Visual Web Developer) does for FTP sites. Watch the bottom of the interface: do you see an indicator that it’s “getting file xxx from the web. Press ESC to cancel”? When you first open a remote FTP site, the entire remote directory is pulled down to your local machine, and stored in a temp directory on your machine with the name VWDWebCache (at least it was called that on my Visual Web Developer Express 2008 install). XP sp3 was stored in

C:\Documents and Settings\[MyNAME]\Local Settings\Temp\VWDWebCache\ftp_[domainname]_[rootdir]\

It also gets the entire cache at various other times. This can be painful for a large directory.

There are certainly no options for it in the property page for the FTP site in Solution Explorer.

Note that you can at least “press ESC to cancel”, to stop it downloading.

Note as well that when you edit a file, it’s pulled into that same cache, and if you do a “file>save as”, you’ll see that the file you’re editing is really now a local copy. That makes sense, of course, in that you could lose the connection to the remote server. At least you’d still have the local copy. When you do a save, the cache folder version of the file is actually pushed up to the FTP site.

Popularity: 72% [?]

Macs interact well with Windows, and with CoRD the experience is a bit smoother. Great for working on the office terminal server, administrating servers or any other time you’d like your PC to be a bit closer without leaving your Mac.

Popularity: 91% [?]

Applies To:
Microsoft Windows Server 2003
Background:
To edit the IIS metabase file without stopping IIS, you must enable Edit-While-Running.
Procedure:
To enable metabase edit-while-running using IIS Manager

1. In IIS Manager, right-click the local computer, and then click Properties.
2. Select the Enable Direct Metabase Edit check box.

Popularity: 57% [?]

When Windows Server 2003 was released was that when our clients attempted to upload media to our product, it was a bit hit and miss at times. What we discovered was a security precaution in IIS 6 limited the maximum file size that was up-loadable to 240Kb.
To resolve this issue, we increased the Maximum ASP upload by running the following from the command line:

cscript C:\inetpub\adminscripts\adsutil.vbs set w3svc/ASPMaxRequestEntityAllowed 10484880

Finding the ASPMaxRequestEntityAllowed node, and changing the value.

With Windows Vista and Windows Server 2008, the way to set this changed again! To achieve the same setting, it can now be done via the IIS Administrative tool. To change do the following:

• Open IIS Manager from the Administrative Tools
• Select the Server from the tree structure on the left hand side
• Double click on ASP in the right pane.
• You will see a list of properties, Expand the Limits Properties and you will see Maximum Request Entity Body Limit. Set the value here in bytes to the upload limit you wish to set. Click Apply.

There is a similar limit imposed in all flavours of ASP.net. This can be configured in the machine.config file of the machine or in the web.config for the application. Adding the following under the <system.web> tag in the will increase the ASP.net maximum upload to 10Mb in this example.

<system.web>
      <httpRuntime maxRequestLength="102400" />
</system.web>

As you can see, it isn’t too difficult to resolve this issue, although the way to change the setting can be difficult at first to find.
I hope this guide makes it a little easier for you.

Popularity: 100% [?]