Xbap download gets 404 not found for a DLL

I've setup IIS for deploying an xbap application. I navigate to the page and it starts to download, but I get a 404 not found error for a DLL I'm trying to include:

ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* An exception occurred while downloading the application. Following failure messages were detected:
+ Downloading
http://localhost/TaxBap/XamlUtils.dll did not succeed.
+ The remote server returned an error: (404) Not Found.

However, this file is in the directory. I can see it from IIS as well. Why would I get a 404 here My application uses an Images directory and I got a 404 for that. I copied the Images directory and the 404 went away. I thought the same thing would happen for a DLL.

Could there be some permissions that prevent a DLL from downloading Or do I have to do some Click Once magic



Answer this question

Xbap download gets 404 not found for a DLL

  • TYTYTY

    What XBAP template are you using Are you actually seeing this with the default templates that come with "Orcas" tools I don't see that on my machines with latest CTPs. If you're using a custom project template, I am not sure if I can help.



  • mimesis

    Ah, I see. We'll correct the SDK article. That was indicative of a past CTP of the Orcas tools. I don't think there are any current issues with Publishing XBAPs from within VS using the latest Orcas CTP. Sorry for the confusion.

  • bilalso

    What CTP are you referring to Afaik, the Publish functionality for XBAPs is fairly ironed out. I don't expect any more feature work to happen there. Are you using the default templates that ship with Fidalgo/Orcas tools

    Some questions/suggestions:

    1. Did you configure all of the MIME types on your web server
    2. Can you try setting the MapFileExtensions property with value true in the project file That will add the .deploy extension to all your binary files so you don't have to configure MIME types for each one of them. During deployment, the files will be recognized for what they are.
    3. What happens when you Publish to a network path or local machine path and launch the app from there Does it work

    Please clear your ClickOnce cache on the client machine before trying any of the above.



  • johnb01

    Well, it looks like my machine is just corrupted due to installs/uninstalls of the previous CTPs. Karen got me connected with Anthony C (private email) on a related issue and some problems boiled down to the same issue.

    Anthony said that the GUID entry I have in the registry is correct. In case someone else runs into this problem, I thought I would post some comments from Anthony:

    My assumption is that this issue is from pervious install that did not clean up correctly.

    The tag you are removing tells VS what project system to use to load your project removing it means it tries to use the default language project which seems to work because Net FX 3 is really based on Net FX 2. This will likely get you by but I would not suggest going long term like this. Potential problems you may face in the future is some features may not work like Add service reference and project upgrade into the full Orcas later on won't work without this tag. The only other suggestion I have is to try it on a clean box and see if you see the same issue.

    I'm due for a machine refresh pretty quick, so maybe I'll try publishing again with everything refreshed.


  • Yitzhak Khabinsky

    I've done some tests with the ClickOnce xbap deployment from VS and it doesn't seem to work properly. Whenever I publish, I get two errors telling me it failed to copy the "<appname>.applcation" file to two places. When I look in the compilation output directory, I see that it did not create the deployment manifest (i.e., .application) file. This is why it can't be copied...it doesn't exist. The application manifest file (<appname>.exe.manifest) is generated.

    I tried messing with MageUI a little bit to see if I could create a proper deployment manifest file, but so far have not had success.

    Getting away from my original scenario, I just made a simple "hello world" xbap (I'm not even trying the extra DLL anymore). I can run this just fine in the debugger; I just can't deploy it. Here are the official errors I get from publishing:

    Error: Failed to copy file 'D:\StandaloneBrowserApp\bin\Debug\StandaloneBrowserApp.publish\StandaloneBrowserApp.application' to 'http://localhost/MyBap/StandaloneBrowserApp.application'. Unable to add 'StandaloneBrowserApp.application' to the Web. Unable to add file 'StandaloneBrowserApp.application'. The system cannot find the file specified.

    Error: Failed to copy file 'D:\StandaloneBrowserApp\bin\Debug\StandaloneBrowserApp.publish\StandaloneBrowserApp.application' to 'http://localhost/MyBap/StandaloneBrowserApp_1_0_0_0.application'. Unable to add 'StandaloneBrowserApp_1_0_0_0.application' to the Web. Unable to add file 'StandaloneBrowserApp_1_0_0_0.application'. The system cannot find the file specified.


  • PaulC VS SQL 2005

    I believe Publish won't work for XBAPs unless you install the VS extensions for .NetFX3.0.

    Since July CTP doesn't have a build of Cider, a matching VS extensions for the July CTP was not released.

    I believe you need the following to be true to have publish work properly:

    1) use a .csproj/.vbproj that includes the the project type guids. These tell VS to load the VS Project Flavor that comes with the VS extensions.
    2) have the VS Extensions installed. (note, if you are using the July CTP, you can still download and install the June CTP version of the VS Extensions by using a command line switch documented here: http://blogs.msdn.com/jaimer/archive/2006/07/25/677679.aspx)

    Hope that helps.

    Thanks, Rob Relyea
    Program Manager, WPF Team
    http://rrelyea.spaces.live.com


  • RScero

    My assumption that xbap deployment is still under construction comes from the comment that it doesn't work from the VS2005 publish wizard (see bottom of this article http://windowssdk.msdn.microsoft.com/en-us/library/ms742303.aspx).

    I have configured the MIME types and IIS according to this article: http://windowssdk.msdn.microsoft.com/en-us/library/ms752346.aspx
    BTW...very handy that someone included the .vbs code to create the MIME types...nice touch

    By "publishing to", I'm just copying the files to a virtual directory, as the article says the Publish wizard doesn't work. So far, I have only tried deploying it on localhost.

    I'll try your other recommendations to see if they solve my problems.

    Thanks


  • Shailendra Kumar

    From what I can dig up, the deployment scenario for Xbap applications is still under construction. It is clear that you cannot use the Publish tab on the Visual Studio project properties page yet. I have read the manual deployment instructions, but do not see any special instructions for deploying .dll files. Could I possibly need a ".manifest" file for the assembly Or perhaps I need to turn it into a ".dll.deploy" file (even though my .exe isn't a .deploy file).
  • Niksta

    When publishing XBAPs, I occassionally get the "failed to copy file..." errors you have reported. I usually get this resolved by following the steps below:

    1) Clean the solution, delete the obj folder

    2) Re-publish

    If it still doesn't work follow step 1); then manually increment the version number to a higher number and re-publish


  • Ivana Hudakova

    Hi,

    After following the above points mainly the 2 item changing all the application files extensions to .deploy cleared another error called Application Download Error. By selecting the project properties in vs.net 2005 and publish tab->options button->select rename all application files using .deploy extension.

    Thanks for the information.



  • Tails111

    Ashish, I'm using the WinFX Web Browser Application template. However, I had to remove the <ProjectTypeGuids> section from the .csproj file because VS refuses to open the project if that line is in the .csproj file.

    I just made a simple "Hello World" in the Browser Application and tried publishing it, and it gives me those errors.

    I don't know what the <ProjectTypeGuids> entry does. With your latest help, I've been able to use the Cider editor again, and I still don't have those guids in my .csproj. After a little more research, I see that {60dc8134-eba5-43b8-bcc9-bb4bc16c2548} has an entry in my registry with very little information. Here is the registry dump:

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\Projects\{60dc8134-eba5-43b8-bcc9-bb4bc16c2548}]
    "Package"="{b3bae735-386c-4030-8329-ef48eeda4036}"

    Compared to everything else under Projects, it seems like something is missing here. I've tried removing/reinstalling Orcas, but that hasn't fixed things. Could the installer be failing somehow


  • Xbap download gets 404 not found for a DLL