------ Build started: Project: CUOnlineManager, Configuration: Debug Any CPU ------
CUOnlineManager -> E:\Vault\CUOnlineManager3\CUOnlineManager\bin\CUOnlineManager.dll
------ Publish started: Project: CUOnlineManager, Configuration: Debug Any CPU ------
Connecting to E:\E\55...
Publishing folder /...
Publishing folder App_Data...
Publishing folder BusCards...
Publishing folder BusCards/Images...
Publishing folder Clearance...
Publishing folder Controls...
Publishing folder CoordinationOffice...
Publishing folder Coordinator...
Publishing folder culogin...
Publishing folder DarkReports...
Publishing folder DateSheet...
Publishing folder DirectorConsole...
Publishing folder DirectorConsole/COMSIS...
Publishing folder DirectorConsole/CUPortal...
Publishing folder DirectorConsole/FacultyFolder...
Publishing folder DirectorConsole/Library...
Publishing folder DirectorConsole/StudentFee...
Publishing folder Faculty...
Publishing folder Faculty/Portal...
Publishing folder FacultyManagement...
Publishing folder FeedBack...
Publishing folder FeedBack/CSS...
Publishing folder FeedBack/FacultyRepeaterReports...
Publishing folder FeedBack/images...
Publishing folder FeedBack/Reports...
Publishing folder FeedBack/Scripts...
Publishing folder HOD...
Publishing folder HOD/Attendance...
Publishing folder HOD/EmployeeAttendance...
Publishing folder HOD/FacultyFolder...
Publishing folder HOD/Offices...
Publishing folder HOD/Reports...
Publishing folder HOD/Students...
Publishing folder HR...
Publishing folder images...
Publishing folder Library...
Publishing folder obj...
Publishing folder obj/Debug...
Publishing folder obj/Debug/Refactor...
Publishing folder obj/Debug/TempPE...
Publishing folder obj/Release...
Unable to add 'obj/Release/CUOnlineManager.dll' to the Web site. Unable to add file 'obj\Release\CUOnlineManager.dll'. The system cannot find the file specified.
Unable to add 'obj/Release/CUOnlineManager.pdb' to the Web site. Unable to add file 'obj\Release\CUOnlineManager.pdb'. The system cannot find the file specified.
Publishing folder Officers...
Publishing folder resources...
Publishing folder resources/css...
Publishing folder resources/images...
Publishing folder resources/images/icons...
Publishing folder resources/img...
Publishing folder resources/jqueryUI...
Publishing folder resources/jqueryUI/base...
Publishing folder resources/jqueryUI/base/images...
Publishing folder resources/jqueryUI/redmond...
Publishing folder resources/jqueryUI/redmond/images...
Publishing folder resources/jqueryUI/themes...
Publishing folder resources/jqueryUI/themes/base...
Publishing folder resources/jqueryUI/themes/base/images...
Publishing folder resources/jqueryUI/themes/redmond...
Publishing folder resources/jqueryUI/themes/redmond/images...
Publishing folder resources/jqueryUI/ui...
Publishing folder resources/jqueryUI/ui/design...
Publishing folder resources/jqueryUI/ui/i18n...
Publishing folder resources/jqueryUI/ui/minified...
Publishing folder resources/scripts...
Publishing folder resources/timepicker...
Publishing folder resources/timepicker/include...
Publishing folder resources/timepicker/include/ui-1.10.0...
Publishing folder resources/timepicker/include/ui-1.10.0/ui-lightness...
Publishing folder resources/timepicker/include/ui-1.10.0/ui-lightness/images...
Publishing folder SMS...
Publishing folder StudentAffairs...
Publishing folder StudentManagement...
Publishing folder theme...
Publishing folder theme/resources...
Publishing folder theme/resources/css...
Publishing folder theme/resources/images...
Publishing folder theme/resources/images/icons...
Publishing folder theme/resources/scripts...
Publishing folder theme/resources/scripts/lib...
Publishing folder theme/resources/scripts/tests...
Publishing folder theme/resources/scripts/tests/functional...
Publishing folder theme/resources/scripts/tests/unit...
Publishing folder TimeTable...
Publishing folder bin...
Publishing folder bin/bin...
Publishing folder bin/obj...
Publishing folder bin/obj/Debug...
Publishing folder bin/_sgbak...
========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped ==========
========== Publish: 0 succeeded, 1 failed, 0 skipped ==========
If you have multiple projects in your solution, try rebuilding each one separately 1st then build your main project and publish.
Sometime I would notice behaviour like this in 2008, ALSO make sure your building in debug mode for pdb files to be created.
separately, try upgrading the solution as soon as you can to VS2012/13
Related
I have an incredibly simple .NET core console application that I'd like to publish into a self contained executable. My application uses an the Microsoft.Extensions.Configuration.Json package so I can use an appsettings.json file.
From the command line, in the .csproj folder, I run
dotnet publish --self-contained true -r win-x64
. Inside my Debug folder, I see a netcoreapp2.1 folder and then the win-x64 folder. Inside that folder, I see the following:
publish -> folder
myapp.deps.json
myapp.dll
myapp.exe
myapp.pdb
myapp.runtimeconfig.dev.json
myapp.runtimeconfig.json
appsettings.json
hostfxr.dll
hostpolicy.dll
Am I supposed to copy just the files from this directory or do i have to copy the entire publish folder along with the files to my destination on a Windows Server? Or did I miss a switch to condense these items down further so movement from server to server is even simpler?
Copying just the files from the win-x64 directory was not enough. I needed to copy up the entire publish folder and run the application from that directory, otherwise error messages such as not being able to find a dependency would occur.
I want to deploy my nuxt.js project on a windows server, plesk shared web host.
I have done the following steps:
I have build project using 'node_modules/nuxt/bin/nuxt-start'
copy .next folder to httpdocs folder in server
copy 'nuxt.config.js' to httpdocs folder
copy 'package.json' to httpdocs folder
deleted web.config file
In the field Application Startup File you have to put node_modules/nuxt/bin/nuxt-start
installed npm packeges on server
but it does not run on the server and I get the following error:
This site can’t be reached
what is wrong?
What are the correct steps to deploy nuxt project on plesk?
Thank you
I added NLog.Config 4.5.4 nuget package to my dotnet core application project.
This package created link to file %USERPROFILE%.nuget\packages\nlog.config\4.5.4\contentFiles\any\any\NLog.config.
When I try to delete this link got error message
"Unable to erase files or folders: Can't modify file 'NLog.config', item doesn't belong the project and was imported from \obj\MyProject.csproj.nuget.g.props"
Then I created new file NLog.config in project folder, but when I build project this file is ignored and copied linked one.
I am trying to learn to build a web application using .net core, mvc x and csharp. I am using visual studio code in OS X.
Here are the files and folders inside the freshly generated project directory:
Controllers
Dockerfile
Program.cs
Properties
README.md
Startup.cs
Views
appsettings.json
bower.json
bundleconfig.json
project.json
web.config
wwwroot
I think the following should be excluded and what else?
bin/
obj/
.vscode
wwwroot
I don't particularly exclude .vscode. It's convenient to share your tasks and debug profiles with others.
This is my .gitignore
node_modules/
**/bin/
**/obj/
**/*.VC.db* #vscode local database files
.vs/ #your friends who use visual studio
project.lock.json
TestResults/
.idea.* #ever heard of Jetbrains Rider?
**/appsettings.production.json
npm-debug.*
I have a finished web project ready to publish. It works fine when I run it in Visual Studio. Then I go to publish it. Visual Studio claims the publication was successful, but when I go to the site on IIS it does not work. The published file system doesn't even have the Images folder, and the links to the Scripts and other folders don't work.
To describe what's happening, first I choose Build-->Publish site. I create a publish profile like so:
Then I publish it as a File System and pick the folder:
Then I publish it as Release:
Then I press Publish:
Here is the output of the publish website by Visual Studio:
------ Build started: Project: LangSite, Configuration: Release Any CPU ------
LangSite -> C:\Users\Administrator\documents\visual studio 2013\Projects\LangSite_151209\LangSite_151209\bin\LangSite_151209.dll
------ Publish started: Project: LangSite, Configuration: Release Any CPU ------
Connecting to C:\Users\Administrator\Documents\LangTestSite...
Transformed Web.config using C:\Users\Administrator\documents\visual studio 2013\Projects\LangSite_151209\LangSite_151209\Web.Release.config into obj\Release\TransformWebConfig\transformed\Web.config.
Copying all files to temporary location below for package/publish:
obj\Release\Package\PackageTmp.
Publishing folder /...
Publishing folder Areas...
Publishing folder Areas/HelpPage...
Publishing folder Areas/HelpPage/Views...
Publishing folder Areas/HelpPage/Views/Help...
Publishing folder Areas/HelpPage/Views/Help/DisplayTemplates...
Publishing folder Areas/HelpPage/Views/Shared...
Publishing folder bin...
Publishing folder Content...
Publishing folder fonts...
Publishing folder Scripts...
Publishing folder Views...
Publishing folder Views/Home...
Publishing folder Views/Shared...
Site was published successfully file:///C:/Users/Administrator/Documents/LangTestSite
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
========== Publish: 1 succeeded, 0 failed, 0 skipped ==========
Here is the layout of the file folders in Visual Studio:
And here is the file structure of the published site. Notice, no Images folder:
When I try to go to the site, I get a page of broken links:
Clearly I am not using the publish web project correctly, but I don't see any different way to do it. What am I doing wrong?
Chances are that your images are in the file system, but they are not in your actual project.
You'll want to tell Visual Studio to 'show all files' its one of the icons in the top of the solution explorer. From there you can see the grayed out items show up under the images folder, and right click and "include in project".