Re: Can no longer publish my web site project

Tech-Archive recommends: Fix windows errors by optimizing your registry



Hi Alvin,

Thanks for your response. Trying to ping the machine from the command line
yields "Request timed out."

I am able to connect to the machine via ftp from the command line and
another ftp client, CuteFtp, though.

As for the error log that VS writes out - where is that file written? I
couldn't find anything in the Visual Studio help docs.

And as for attaching to another process, the help docs mention:

"...choose Attach to Process from the Tools menu..."

which doesn't exist. How do I go about attaching to another process?

Thanks for your help

/jason

"Alvin Bruney [MVP]" <some guy without an email address> wrote in message
news:OF1ChhxjHHA.4872@xxxxxxxxxxxxxxxxxxxxxxx
Can you ping the site for the machine, i'd check that first. VS writes an
error log out to disk that you can examine. Another option is to debug the
publish process. Open another copy of visual studio and attach it to the
first copy of visual studio, set it to break on all exceptions. Run the
publish process from the first copy and see what exceptions are thrown in
the second copy when the debug breakpoint catches.

--
Regards,
Alvin Bruney
------------------------------------------------------
Shameless author plug
Excel Services for .NET is coming...
OWC Black book on Amazon and
www.lulu.com/owc
Professional VSTO 2005 - Wrox/Wiley


"Jason" <JasonJason@xxxxxxxxxxxxx> wrote in message
news:u79fDZnjHHA.1216@xxxxxxxxxxxxxxxxxxxxxxx
Hi all,

I am no longer able to publish a web site project using Visual Studio
2005 Professional.

I am publishing it to an FTP url, and this used to work just fine.

I enter the username and password and select "passive mode" when
publishing the site, like I have always done. Visual Studio deletes the
existing files, but then doesn't write the new ones, though it tells me
the operation was successful:


------ Build started: Project: C:\WebDev\WebNet\, Configuration: Debug
.NET ------
Pre-compiling Web Site

Building directory '/WebNet/admin/'.

Building directory '/WebNet/UserControls/'.

Pre-compilation Complete

------ Publish started: Project: C:\WebDev\WebNet\, Configuration: Debug
.NET ------

========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped
==========

========== Publish: 1 succeeded, 0 failed, 0 skipped ==========



I have tried resetting the permissions on the web folder, and also
deleted an re-created the Server Extensions 2002 Web, but to no avail.

Any ideas?

Thanks very much





.



Relevant Pages

  • Re: Publish Web Site
    ... Choose the FTP hosting option instead of the default File System or HTTP options. ... Is it possible to publish a web site through FTP using Visual Studio ...
    (microsoft.public.dotnet.framework.aspnet)
  • [NEWS] Java Sandbox and Stateful Firewalls Interaction
    ... The attacker must lure the victim to a carefully ... The attacker creates a specifically crafted web site. ... The victim's browser downloads the applet and begins to run it. ... A FTP server on the same machine that hosts the originating web site ...
    (Securiteam)
  • Re: Access Application to Visual Studio
    ... I have written several FTP clients using .Net. ... > I do agree that this Access developer should probably stick with Access. ... > There are plenty of third-party companies out there that use Visual Studio ... > Think of it this way: You can buy a house. ...
    (microsoft.public.vstudio.general)
  • Re: "An error occurred accessing your Windows SharePoint Services site files"
    ... This really sounds like a Visual Studio .NET or ASP.NET problem. ... Start IIS and see if you can browse ... > FrontPage 2002 Server Extensions, or some vestigial junk from SharePoint, ... > to create a new web site in FrontPage 2003. ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Multiple FTP sites on the same server. How?
    ... Server, you create DNS records and add the appropriate host headers to the ... What about multiple FTP sites on the same server? ... Put host headers in for each web site respectively: ... If your system is in a domain, use domain security policy. ...
    (microsoft.public.inetserver.iis.ftp)