I have several MVC3 applications, when I try and publish it doesn't actually publish anything, the output is:
2>obj\Debug\Package\PackageTmp.
2>Deleting existing files...
2>Publishing folder /...
2>
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
========== Publish: 1 succeeded, 0 failed, 0 skipped ==========
Change publish mode from RELEASE to DEBUG (or vice versa), publish, change again and publish again.
Related
After update my vs2017 to 16.6.5, and update google sdk-build-tools to 27.0.3, my project got a problem with debugging for my tablet. My project type is xamarin.android, I check it for xamarin.forms but debugging for my (not emulator) tablet is woks! Also before this update i don't have any problem with debugging.
Here is my project output in diagnostic mode:
3>Done executing task "Delete".
3>Using "AndroidZipAlign" task from assembly "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\Xamarin\Android\Xamarin.Android.Build.Tasks.dll".
3>Task "AndroidZipAlign"
3>Task Parameter:Source=F:\Projects\Amin\AminApp\AminApp\obj\Debug\android\bin\com.aminsystem.forush.apk
3>Task Parameter:DestinationDirectory=bin\Debug\
3>Task Parameter:ToolPath=C:\Program Files (x86)\Android\android-sdk\build-tools\27.0.3
3>AndroidZipAlign Task
3> Alignment: 4
3> Source: F:\Projects\Amin\AminApp\AminApp\obj\Debug\android\bin\com.aminsystem.forush.apk
3> DestinationDirectory: bin\Debug\
3>C:\Program Files (x86)\Android\android-sdk\build-tools\27.0.3\zipalign.exe 4 "F:\Projects\Amin\AminApp\AminApp\obj\Debug\android\bin\com.aminsystem.forush.apk" "bin\Debug\\com.aminsystem.forush-Signed.apk"
3>Done executing task "AndroidZipAlign".
3>Task "AndroidZipAlign"
3>Task Parameter:Source=F:\Projects\Amin\AminApp\AminApp\obj\Debug\android\bin\com.aminsystem.forush-armeabi-v7a.apk
3>Task Parameter:DestinationDirectory=bin\Debug\
3>Task Parameter:ToolPath=C:\Program Files (x86)\Android\android-sdk\build-tools\27.0.3
3>AndroidZipAlign Task
3> Alignment: 4
3> Source: F:\Projects\Amin\AminApp\AminApp\obj\Debug\android\bin\com.aminsystem.forush-armeabi-v7a.apk
3> DestinationDirectory: bin\Debug\
3>C:\Program Files (x86)\Android\android-sdk\build-tools\27.0.3\zipalign.exe 4 "F:\Projects\Amin\AminApp\AminApp\obj\Debug\android\bin\com.aminsystem.forush-armeabi-v7a.apk" "bin\Debug\\com.aminsystem.forush-armeabi-v7a-Signed.apk"
3>Output file 'bin\Debug\\com.aminsystem.forush-armeabi-v7a-Signed.apk' exists
3>"zipalign.exe" exited with code 1.
3>Done executing task "AndroidZipAlign" -- FAILED.
3>Done building target "_Sign" in project "AminApp.csproj" -- FAILED.
3>Done building project "AminApp.csproj" -- FAILED.
3>Build FAILED.
3>
3>Deploy failed on Samsung SM-T585
========== Build: 2 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========
As you see my project compiled successfully!
I also tried copy zipalign.exe from Android\android-sdk\build-tools\27.0.3 to Android\android-sdk\tools, but it not works.
The problem was solved by changing the Debug option to X86!
Thanks to https://www.c-sharpcorner.com/forums/deployment-error-with-xamarin-android-application
In my case, zipalign.exe was being blocked by the Windows Virus & Threat protection and once I allowed it, it started working fine.
I am trying to do a basic 'cloud project' -> 'Asp.Net Web Application' in VS2017
When I debug the application I get what I expect the 'MVC landing page'.
Then when I publish i get an Azure landing page, but I was expecting to see my 'MVC landing page'
It appears to deploy correctly, so I must be doing missing something obvious.
When I publish project from VS2017 I get this:
1>------ Build started: Project: zerocloud, Configuration: Release Any CPU ------
1> zerocloud -> C:\Users\patrick\Documents\Visual Studio 2017\Projects\zerocloud\zerocloud\bin\zerocloud.dll
2>------ Publish started: Project: zerocloud, Configuration: Release Any CPU ------
2>Transformed Web.config using C:\Users\patrick\Documents\Visual Studio 2017\Projects\zerocloud\zerocloud\Web.Release.config into obj\Release\TransformWebConfig\transformed\Web.config.
2>Auto ConnectionString Transformed Views\Web.config into obj\Release\CSAutoParameterize\transformed\Views\Web.config.
2>Auto ConnectionString Transformed obj\Release\TransformWebConfig\transformed\Web.config into obj\Release\CSAutoParameterize\transformed\Web.config.
2>Copying all files to temporary location below for package/publish:
2>obj\Release\Package\PackageTmp.
2>Start Web Deploy Publish the Application/package to https://zerocloud20170318070155.scm.azurewebsites.net/msdeploy.axd?site=zerocloud20170318070155 ...
2>Adding ACL's for path (zerocloud20170318070155)
2>Adding ACL's for path (zerocloud20170318070155)
2>Updating file (zerocloud20170318070155\bin\zerocloud.dll).
2>Adding ACL's for path (zerocloud20170318070155)
2>Adding ACL's for path (zerocloud20170318070155)
2>Publish Succeeded.
2>Web App was published successfully http://zerocloud20170318070155.azurewebsites.net/
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
========== Publish: 1 succeeded, 0 failed, 0 skipped ==========
The website (http://zerocloud20170318070155.azurewebsites.net/) does load correct. Any chance you could be seeing a cached version?
This is what I see:
I am using visual studio 2008. I configured OpenCV with Visual studio. But i am getting the following error.
1>Copyright (C) Microsoft Corporation. All rights reserved.
1>fatal error RC1109: error creating .\Debug\OPEN_CV_TEST.exe.embed.manifest.res
1>Project : error PRJ0002 : Error result 1 returned from 'C:\Program Files\Microsoft SDKs\Windows\v6.0A\bin\rc.exe'.
1>Build log was saved at "file://c:\Users\GARGI\Documents\Visual Studio 2008\Projects\OPEN_CV_TEST\OPEN_CV_TEST\Debug\BuildLog.htm"
1>OPEN_CV_TEST - 1 error(s), 0 warning(s)
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
Can somebody please explain?
Are you sure it's related to OpenCV ?
The RC1109 error happens sometimes if Visual Studio try to create a file in a "read only" folder. I would recommend digging that way.
I have Frank D Lunas directx11 book, and i'm trying to set it up using VS2012, but i've run into this:
1>------ Build started: Project: FirstProject, Configuration: Debug Win32 ------
1>TRACKER : error TRK0002: Failed to execute command: "C:\Users\Josh\Documents\Applications\DirectX\Utilities\bin\x64\fxc.exe /nologo /Emain /Fo "C:\Users\Josh\Documents\DirectX\Chapter 1\Projects\FirstProject\Debug\color.cso" /Od /Zi FX\color.fx". The handle is invalid.
1>
1>
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
and I have no idea how to fix it.
I believe I have all the paths correct, and included files.
Any ideas?
Thanks!
I'm trying to get into NDS Homebrew,
and have installed devkitPro and PALib, and linked it with Visual Express 2008.
But When I try to compile the Hello World example code that is automatically generated when you start a new NDS project, I get the following error:
1>------ Build started: Project: newtest, Configuration: Release Win32 ------
1>Performing Makefile project actions
1>Linking...
1>c:/devkitpro/devkitarm/bin/../lib/gcc/arm-eabi/4.6.1/../../../../arm-eabi/lib/ds_arm9_crt0.o: In function `CIDLoop':
1>(.init+0x1c0): undefined reference to `__libnds_mpu_setup'
1>c:/devkitpro/devkitarm/bin/../lib/gcc/arm-eabi/4.6.1/../../../../arm-eabi/lib/ds_arm9_crt0.o: In function `CIDLoop':
1>(.init+0x210): undefined reference to `initSystem'
1>c:/devkitpro/devkitarm/bin/../lib/gcc/arm-eabi/4.6.1/../../../../arm-eabi/lib/ds_arm9_crt0.o: In function `CIDLoop':
1>(.init+0x21c): undefined reference to `__libnds_exit'
1>collect2: ld returned 1 exit status
1>make[1]: *** [/c/DSProjects/newtest/newtest/Release/newtest.elf] Error 1
1>make: *** [build] Error 2
1>Build log was saved at "file://c:\DSProjects\newtest\newtest\Release\BuildLog.htm"
1>newtest - 0 error(s), 0 warning(s)
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
so obviously something is missing or wrong in devkitPro, but can't figure out exactly what and how to fix it.
PAlib is not supported, you broke devkitARM by installing it.
The only advice we have is to uninstall devkitARM completely then reinstall without PAlib. Once you've done that you should ask questions on the devkitPro forums, the gbadev forums, or, if you prefer realtime answers then there's always the IRC channels
Avoid PAlib, PAlib users and PAlib tutorials at all costs.
Obviously something is missing or wrong from PAlib. devkitARM works perfectly fine for me. PAlib is old and very poorly written.