If I publish the code then it is not copying in web folder that exists in wwwroot .
Empty folder is there but while publishing it is saying that Site was published successfully.
After that it open blank browser with message (To Parent Directory)
It is giving no error.
Building directory '/project/Users/'.
Pre-compilation Complete
------ Publish started: Project: F:\...\project\, Configuration: Debug Any CPU ------
Connecting to site E:\project...
Publishing directory /...
========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped ==========
========== Publish: 1 succeeded, 0 failed, 0 skipped ==========
I got the solution
Publish in debug mode first then change settings and publish in release mode. it will surely work :)
Related
Visual Studio 2015.update3 - fully updated & patched - windows 8.1 - .net 4.7.1
2>------ Publish started: Project: Prometheus, Configuration: Release x64 ------
2>Connecting to C:\Temp\publish...
2>Project "test.csproj" (GatherAllFilesToPublish target(s)):
2> Building with tools version "14.0".
2> Target "ValidateMSBuildToolsVersion" skipped. Previously built unsuccessfully.
2>Done building project "test.csproj" -- FAILED.
2>
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
========== Publish: 0 succeeded, **1 failed**, 0 skipped ==========
I have searched and tried every solution online - no joy. Have spent over 3 days trying to sort this out - getting super frustrated now. It appears to build fine but always fails to publish to a local folder on the pc.
Hoping someone can point me in the right direction.
Note: I have tried Any CPU, Debug, and Release configurations - all end the same. I have configured the build to output diagnostic information which is available on request.
I have a WCF web service using Visual Studio 2015. If I have a compile error in C# code, when I publish the web service (to a file location) the "build" will succeed, and continue through a successful publish:
========== Build: 1 succeeded, 0 failed, 1 up-to-date, 0 skipped ==========
========== Publish: 1 succeeded, 0 failed, 0 skipped ==========
If I then deploy to an IIS web server and call the web service there, the call fails and returns a page describing the compilation error.
When publishing, the output in VS starts with Build started: but apparently it isn't really doing a build because any build would have failed, and in fact if I do a build instead of publish, it does report the error(s). Do I have to remember to build before publishing to check for errors, or is there a way to get it to really for realz compile the code?
If solution has many projects then try building them one at a time.
Try below steps:
Restart Visual Studio.
Restart Computer
Rebuild all
Clean Solution then Rebuild All
Also you can check below
Setting the MSBuild project build output verbosity (in Options > Projects and Solutions > Build and Run setting area) to "Diagnostic" as shown below. This then showed that the custom action was what had failed.
https://blogs.msdn.microsoft.com/saraford/2008/10/07/did-you-know-you-can-configure-the-msbuild-verbosity-in-the-output-window-329/
I' trying to publish ClickOnce Application to a webserver through sftp (Using Visual Studio 2015. The server is Centos 6.7).
My final config in the Publish Wizard:
The application will be published to:
sftp://10.1.0.88/home/www/sample/web/desktop/
Users will launch this application from:
http://sample.example.com/desktop/
When I published: (Output)
Connecting to 'sftp://10.1.0.88/home/www/sample/web/desktop/'...
Publishing files...
Publish success.
Warning: Unable to view published application at http://sample.example.com/desktop/publish.htm.
http://sample.example.com/desktop/publish.htm
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
========== Publish: 1 succeeded, 0 failed, 0 skipped ==========
Nothing was added in /home/www/sample/web/desktop/. But it says Publish success.
What should I do?
It turned out the deployment files were added to /root/home/www/sample/web/desktop/instead of /home/www/sample/web/desktop/
So I change publishing folder location from
sftp://10.1.0.88/home/www/sample/web/desktop/
to
sftp://10.1.0.88/../home/www/ecr/web/desktop/
1> IPC-ACE -> C:\Users\Samer.Chemaly\Documents\Visual Studio 2012\Projects\IPC-ACE-1\IPC-ACE\bin\x86\Release\IPC-ACE.exe
1>MakePRI : warning 0xdef00520: Invalid qualifier: 12-SEC
1> IPC-ACE -> C:\Users\samer.chemaly\Desktop\ACE-IPC\IPC-ACE_1.1.0.2_x86_Test\IPC-ACE_1.1.0.2_x86.appx
1>C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\AppxPackage\Microsoft.AppXPackage.Targets(1772,9): error APPX1204: Failed to sign 'C:\Users\samer.chemaly\Desktop\ACE-IPC\IPC-ACE_1.1.0.2_x86_Test\IPC-ACE_1.1.0.2_x86.appx'. SignTool Error: An unexpected internal error has occurred.
1>C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\AppxPackage\Microsoft.AppXPackage.Targets(1772,9): error APPX1204:
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
========== Package: 0 succeeded, 2 failed ===========
This is the error I am getting when I try to create the app package.
The issue was strange! I recreated the app and started to create items page by page and item by item. The issue was in a presentation file available in the assets with and extension .exe
The error that was showing is irrelevant at all but this is for you to know in case you face a similar issue. thank you :)
It really irks me to sit around waiting for "Publishing files..." to finish. I am publishing using FTP, so maybe this is the issue.
Here's what the output looks like:
Connecting to 'ftp://example.com/public_html/download/xxx/'...
Publishing files...
Publish success.
http://example.com/download/xxx/publish.htm
========== Build: 12 succeeded or up-to-date, 0 failed, 0 skipped ==========
========== Publish: 1 succeeded, 0 failed, 0 skipped ==========
In between "..." and "Publish success" is a rather long wait for which I would like a more detailed status.
If you're publishing from Visual Studio, simply show the Output Window and pay attention to it during a publishing process. (Go to View->Output to view the Output window.)
The Output window displays build info, errors and the status of the ClickOnce publication process. When you publish your application, ClickOnce has to generate a few files and then it publishes all of the associated file with your project. When it is copying your files to the publication server, each file that has been updated is enumerated in the Output window, complete with a x of n count.
Hope that helps.
No, there's no way to enumerate those files as they are published for a client application. I think it does it for a VSTO app, but not for a regular client application.
I'll turn this into the PM at MSFT again as a frequently requested item.