| Frequenty Asked Questions |
 |
What versions of Visual Studio is Dispatch compatible with?
Dispatch is compatible with Visual Studio 2005 / 2008 /2010. During installation, Dispatch will detect which version
of Visual Studio is installed and target that version. If more than one supported version is installed, you will be asked to choose targeted version(s).
Dispatch can be installed for any version of Visual Studio side-by-side.
..top..
What about MSBuild, NAnt, etc?
Dispatch is a great tool for casual web-app deployment and is NOT an intended replacement for build software or enterprise-level applications
that have numerous steps involved in deploying a single build. Dispatch is geared towards developers and design firms focusing on smaller
web applications, or projects that can be deployed on a per-file basis. Dispatch eliminates the need for a dedicated FTP client application
and helps keep track of the files that need to be uploaded - all from within the comfort of the IDE.
..top..
What FTP server software is Dispatch compatible with?
Currently, Dispatch has only been tested to work with Microsoft FTP that is packaged with Windows Server.
Moderate testing has been performed on PureFTPd for Linux servers. Stronger compatibility with other FTP server software
is in the works.
..top..
What types of web site projects are supported?
Only web projects that are stored locally are supported. This includes File System and Local IIS. Sites that are
not supported include FTP and HTTP.
..top..
What editions of Visual Studio will Dispatch work with?
Dispatch is compatible with all editions of Visual Studio 2005 except the Express versions. This is a limitation
imposed by Microsoft.
..top..
Does Dispatch support SSL?
Does Dispatch support multiple configration modes (i.e. staging, production, etc)?
Yes. Dispatch supports multiple deployment modes allowing you to deploy a single project to multiple
FTP servers. Please see the Deployment Modes topin in the help section.
..top..
Does Dispatch have any keyboard shortcuts?
When I'm editing a file and I press the keyboard shortcut to Upload the file, nothing happens.
In order to use the keyboard shortcut (default: alt + u), Track Active Item in Solution Explorer must be enabled. You
can find this option in Visaul Studio Options: Tools > Options > Projects and Solutions
..top..
Dispatch doesn't seem to be tracking my changed items. What's going on?
Check your Dispatch settings in Tools > Options > Dispatch. Ensure the Track Changed Items checkbox is checked.
..top..
Why does the installation take so long?
Installation can take several minutes to run. The last step in the installation forces Visual Studio to recache the UI
for any installed packages and can take several minutes to complete. Unfortunately, this is a necessary step
when upgrading to a newer version that has UI changes.
..top..
I've lost my key? Is there any way to look it up?
My codebehind (.cs / .vb) files aren't being uploaded. What's going on?
Codebehind files are ignored if you are using Web Application Projects or ASP.NET MVC Projects. Since the site is compiled into
an assembly, the codebehind files aren't needed on the web server.
..top..
When I launch Visual Studio, I get a "Package Load Failure" warning prompt. How can I fix this?
This error can occur if Visual Studio cannot load the Dispatch package assembly properly. This can be due to a number of reasons
so the first thing to do is enable logging withing Visual Studio during the package load phase.
To do this, run the following command:
C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\devenv.com /resetskippkgs /log "C:\Temp\VSLog.xml"
Let Visual Studio load and display the "Package Load Failure" prompt, then close down Visual Studio. It's important
to close down Visual Studio otherwise the log file will be incomplete. Then, please email the log file to support@yellowcup.net
so we can attempt to locate the issue.
..top..
Visual Studio crashes without any notice after I open a solution with a web project in it. Is Dispatch causing this?
Indirectly, yes. Any Visual Studio package (including the Microsoft Azure package) can cause Visual Studio to crash due to a bug in the CLR.
If you suspect this may be happening to you, check your Event Viewer and look for a crash event with the following description:
NET Runtime version 2.0.50727.3074 - Fatal Execution Engine Error (706D5FC0) (80131506)
Microsoft has acknowledged the issue and has distributed a patch that should fix the issue. Here is a post which describes the issue in
greater detail and provides a link for both 32 & 64 bit systems:
http://blogs.msdn.com/webdevtools/archive/2009/03/03/hotfix-available-for-asp-net-mvc-crashes-with-azure-power-commands-resharper.aspx
Don't forget to restart your system after you have applied the patch.
..top..
|
|