I'd like to create 2 apps from the same project(VS solution), both of them has the same functional with small differences. So I just made 2 copies of my solution and I changed solution name, namespace and asigned app to different Microsoft Store app. When I try to instal secnod app on phone I get:
2>caught exception: System.Exception: Install failed. Please contact your software vendor. (Exception from HRESULT: 0x80073CF9)
2> at Windows.Foundation.IAsyncOperationWithProgress`2.GetResults()
2> at Microsoft.VisualStudio.ImmersiveProjectServices.PlatformShim.AppxCancelableDeployOp.Microsoft.VisualStudio.ImmersiveProjectServices.PlatformShim.IAppxCancelableDeployOp.Execute()
2> at Microsoft.VisualStudio.ImmersiveProjectServices.Shared.AppxLayoutManager.RunDeployOpWithCancel(IAppxCancelableDeployOp deployOp, CancelManager cancel)
2> at Microsoft.VisualStudio.ImmersiveProjectServices.Shared.AppxLayoutManager.RegisterPackage(String location, DeployPackageName deployPackageName, CancelManager cancel)
2> at ImmersiveDeploy.Program.ExecuteTask(String[] args, Int32 argument, XDocument immersiveDeployResults, ImmersiveDeployTask task, DeployPackageName deployPackageName)
2> at ImmersiveDeploy.Program.Main(String[] args),
2>
2>*** End of logging from deployment agent ***
2>Error : DEP0001 : Unexpected Error: Install failed. Please contact your software vendor. (Exception from HRESULT: 0x80073CF9)
========== Build: 1 succeeded, 0 failed, 1 up-to-date, 0 skipped ==========
========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========
Projects build report:
Status | Project [Config|platform]
-----------|---------------------------------------------------------------------------------------------------
Succeeded | BackgroundTaskRawNotification\BackgroundTaskRawNotification.csproj [Debug|x86]
Succeeded | MySolution\MyApp.csproj [Debug|x86]
Failed | MySolution\MyApp.csproj [Debug|x86]
As is mentioned in other questions, if I uninstall one of them, the second is installing but I'd like to made some changes to install both of them. Have to mention that on PC I can install both apps from Visual Studio with no errors.
I am using:
Windows 10 Pro
Visual Studio Version 14.0.24720.00 Update1
Mobile Emulator 10.0.10240.0
Any advices are appreciated.
P.s. In android we have gradle flavors that helps us to build different apps from the same Android Studio project, maybe there is something similar in Visual Studio?
The purpose of reserving multiple names for an App is that the name has meaning for different languages. E.g. an English speaking person would understand "My Great App" and a German speaking e.g. "Meine tolle App". When you assign multiple names to the same App which is identified by it's ID you do not have two Apps but just one with multiple names. That is why you're getting the error.
You could try to change these IDs manually but the easiest, fastest and safest way would be to just let Visual Studio do the work by creating a new project and copy/paste/include your files.
Anyway if your intention is to create a "Free" and a "Pro" version you should consider doing it the recommended way and use in App purchases or create a trial version.
In the package.appxmanifest file, in the Package tab change the Package Name value. Notice how changing this will also change the Package Family Name as well.
Lastly, change the Display Name from the Application tab so you can differentiate the apps when ruuning.
Related
This is re-Question about issue "SignTool Error: Access is denied." on my visual studio.
When I compile "SideLoad" application on Visual Studio 2017. This error happened again.
This is not first time for me. Previously, I could not resolve this error. Then, I bought New DELL PC :( Yes, During some period, It worked fine without any problem. but I saw same error again, Today !
Here is some additional information.
x64, Windows 10, Os ver 1703 , Build 15063.675.
Visual Studio 2017
This is new PC. Administrator, Local user, not MSN user.
Target version : Windows 10 Creator Update ( 10.0; Build 15063 )
Min version : Windows 10 November Update ( 10.0; Build 10586 )
After build of side load applicaiton, This error show ::
1> Bg7Uwp1 -> D:\develop\visualstudio2\xxx\Bg7Uwp1\Bg7Uwp1\bin\x86\Release\Bg7Uwp1.exe
1> Processing application code
1> Computing application closure and generating interop code
1> Loading 108 modules...
1> Generating code...
1> Interop code generated.
1> Generating serialization code
1> Compiling interop code
1> Generating System.Reflection.DispatchProxy proxy code.
1> Cleaning up unreferenced code
1> Generating native code
1> Generating fixups for native code
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Microsoft\VisualStudio\v15.0\AppxPackage\Microsoft.AppXPackage.Targets(3787,5): error APPX1204: Failed to sign 'D:\develop\visualstudio2\xxx\Bg7Uwp1\Bg7Uwp1\bin\x86\Release\Bg7Uwp1_1.0.9.0_x86.appx'. SignTool Error: Access is denied.
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Microsoft\VisualStudio\v15.0\AppxPackage\Microsoft.AppXPackage.Targets(3787,5): error APPX1204: SignTool Error: An error occurred while attempting to sign: D:\develop\visualstudio2\xxx\Bg7Uwp1\Bg7Uwp1\bin\x86\Release\Bg7Uwp1_1.0.9.0_x86.appx
1>
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Microsoft\VisualStudio\v15.0\AppxPackage\Microsoft.AppXPackage.Targets(3787,5): error APPX1204:
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
========== Package: 0 succeeded, 2 failed ===========
========== App Bundle: 0 succeeded, 1 failed ===========
Please give me some idea. I tried everything from internet and here. but Previously, I could not resolve.. I can not buy new PC again !
Update 1
and After this trouble, I open new Uwp project and start sideload compile. it show same error ! This is same situation with previous PC ! Now, My Vs2017 can not make sideload for an
empty UWP project !!
in previous PC, I tried everything. Re-install VS2017, Re-install NuGet items. but it did not resolve at all. Only way was to buy new PC and re-install VS.
Update 2
With verbose mode of VS2017 compile output, I found , There is signtool.exe in SignAppxPackageExeFullPath=C:\Program Files (x86)\Windows Kits\10\bin\10.0.15063.0\x64\signtool.exe
with it, I tried to sign by myself.
Open command prompt tool with Admin
Run below command. I success to sign !??
Update 3
Next challenge is to add "Admin privilege" with "Signtool.exe" like this. but this was failed. Error was changed. "It need administrator privilege" and it make build error. not success.
Question
If I do sign manually, Is it enough ?
I signed with manual ( target file is : Bg7Uwp1_1.0.19.0_x64.appx ) "c:\Program Files (x86)\Windows Kits\10\bin\10.0.15063.0\x64\signtool.exe" sign /fd SHA256 /a /f Bg7Uwp1_TemporaryKey.pfx bin\x64\Release\Bg7Uwp1_1.0.19.0_x64.appx
Done Adding Additional Store
Successfully signed: bin\x64\Release\Bg7Uwp1_1.0.19.0_x64.appx
I copy all "Release" folder to other PC.
I copy "Bg7Uwp1_TemporaryKey.pfx" to other PC too.
On 2nd PC, I install the certification key first "Bg7Uwp1_TemporaryKey.pfx". Success.
I tried to install with clicking Bg7Uwp1_1.0.19.0_x64.appx
I can not installed : (
Either you need a new certificate installed for this app package, or you need a new app package with trusted certificates. Your system administrator or the app developer can help. A certificate chain processed, but terminated in a root certificate which isn't trusted (0x800B0109)
Find! a solution but Not perfect yet.
with above error, I read this.. This is a step to install sideload application to PC. I follow this. I can resolve the error 0x800B0109.
In File Explorer, right-click on the app package, and in the pop-up context menu select Properties.
In the Properties dialog, select the Digital Signatures tab.
In the Signature list, select the signature and then click the Details button.
In the Digital Signature Details dialog, click the View Certificate button.
In the Certificate dialog, click the Install Certificate… button.
In the Certificate Import Wizard, select Local Machine and then click Next. You will need to grant administrator privileges to continue.
Select Place all certificates in the following store and browse to the Trusted People store.
Click Next, then click Finish to complete the wizard.
after this step, I can install my Sideload to my Own PC. but To install 2nd PC has error. ( New error 0x80073CF3 ) . but I get big improvement !
Update 4 ( Not resolve still ! )
Now, TO install other PC is not impossibile. Dependencies file can not create by VS. because signtool has error.I have to install other PC. Without it, All my time would be waste.. :( please help me...
This is old dependencies files. I have to make it for my ver 19.
Update 5
I check What Vs2017 is doing in background. I used ProcessMonitor. and She execute this command. It look like no problem. I tried with Admin-MS-prompt, It success.
"C:\Program Files (x86)\Windows Kits\10\bin\10.0.15063.0\x64\signtool.exe" sign /fd sha256 /f "Bg7Uwp1_TemporaryKey.pfx" "D:\develop\visualstudio2\shinwatec\Bg7Uwp1\Bg7Uwp1\bin\x64\Release\Bg7Uwp1_1.0.19.0_x64.appx"
but Without Admin, I got same error with VS2017 !
I found the solution ! and fix it.
with ProcessMonitor, I found this line.
signtool.exe has "Access denied" to access %appdata%\local\Temp
I check the folder permission. There is no permission on the Temp folder. I added my own user Networkname\username .
After this. I success to fix this issue. Now my visualStudio 2017 can make sideLoad application ! Yes, I do not need to buy new PC again :)
thank you. Mr. BugFinder.
I have two versions of one application in one project/solution with only one difference - app name.
After installation one of them, the second app cant deploy:
2>Deploying to Phone Internal Storage...
2>Updating the layout...
2>Copying files: Total <1 mb to layout...
2>Checking whether required frameworks are installed...
2>Registering the application to run from layout...
2>DEP0001 : Unexpected Error: -2147009287
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========\
Is there any unique data in Package.appxmanifest or Package.StoreAssociation.xml which should be changed ?
Yes, you need to change the Package.appxmanifest for each app.
In general you need a different Package Family Name for each app you install.
When deploying to a phone things are slightly different. The phone uses an Id for each installed app. This is defined as the PhoneProductId attribute of the PhoneIdentity element in the Package. You need to edit the XML directly to change this. (Right click the file, select 'Open With...' and then select a suitable editor.)
If you're distributing through the store then the project will be associated with the store and so changing the name will not be sufficient to create a new store entry. You'll need a different store association for each entry in the store.
I have Xamarin installed both on my Visual Studio 2015 and my MacBook Pro with OS X 10.11.4. The problem is that when I try to connect from VS to OS X, it says that for some reason it can't start the Designer agent.
As far as I see from the log the main problem is in this:
Xamarin.VisualStudio.IOS.MacServer Error: 0 : [2016-04-03 21:21:44.1336] An error occured starting the Designer 4.0.3.214 agent: Xamarin.Messaging.Client.AgentConsoleRunner Information: 0 : ==== :: Xamarin :: 4.0.3.214-cycle6-c6sr3+0dd817c ====
Xamarin.Messaging.Client.AgentConsoleRunner Information: 0 : Starting Designer 4.0.3.214...
Failed-Native type size mismatch between Xamarin.Mac.dll and the executing architecture. Xamarin.Mac.dll was built for 32-bit, while the current process is 64-bit.
Is there any way to fix it? Btw, here is the full log http://pastebin.com/iB6X0XWe
I see a number of issues in that log. One that caught my eye is that it failed to download provisioning profiles. Make sure that XCode is installed (and up to date) and that you can run it. You might also need to log in to the Apple dev portal and accept a license agreement - sometimes the portal will block some actions if there is a pending agreement.
Also, it looks like your Xamarin install on OSX might be slightly different (or might be on different channel):
There is a mismatch between the installed Xamarin.iOS (version 9.6.1.9) on the Mac MacBook-Pro-Andrey.local (192.168.0.3) and the local Xamarin.iOS 9.6.1.8. While this may not be an issue, it might cause unexpected behaviors. When applying updates, make sure to keep both the Mac and Windows in sync.
I would fix that first before doing anything else.
I have now had an error with VS2013 and WP8.1 silverlight for a couple of days.
I get a couple of different errors, ..Ensure unlocked screen.., AgHost.exe could not be launched, port is in use by another program and ensure the device is unlocked.
These errors came suddenly after I retarged the solution. I have no compiling errors.
Solution Attempts
Restart PC
Restart program
unregister and reregister the phone
reinstall Update 3
reinstall VS2013
Windows Phone 8 Application crash once its launched AgHost.exe' has exited with code -532265403
Install VS2015 with no luck.
reinstall VS2013 Update 4
Nothing worked. The error is also the same for emulator as well as different devices. I can however get the release mode installed. Break points can be used when using release mode, but I have to Clean, Rebuild and then deploy for every time I want to deploy the application. Further the deploy time has gone up exponentially. Before upgrading I used a maximum of 10 seconds. Now it is above a minute in wait time. :/
Anyone has a solution for this ?
Extra
If I run the solution before upgrade on device or Emulator It spins up with debugger. If then go to the updated WP81, I get a popup with info Something is taking longer then normal and then it crashes with ..Ensure unlocked screen.. :/
Could it be an issue with the differen SDKS?
During a repair of all the SDKs, I found an issue with the event log, which I cleared based on The Event Log File is full
Still no success.
Extra
I cannot spin up the emulator from VS2013, when using the WP8.1 solution, but the wp8.0 solution in the same VS works :S
I found an error in a log file, from:
The errors are:
[0F08:14A8][2015-07-23T09:11:44]: Applying execute package: silverlight5_DRT, action: Repair, path: C:\ProgramData\Package Cache\DEB5078B60B74431E2830831EB48DF129CB32932\packages\Silverlight\5.0_DRT\Silverlight_Developer.exe, arguments: '"C:\ProgramData\Package Cache\DEB5078B60B74431E2830831EB48DF129CB32932\packages\Silverlight\5.0_DRT\Silverlight_Developer.exe" /q /ignorewarnings'
[0F08:14A8][2015-07-23T09:11:45]: Error 0x800705de: Process returned error: 0x5de
[0F08:14A8][2015-07-23T09:11:45]: Error 0x800705de: Failed to execute EXE package.
[0550:0E74][2015-07-23T09:11:45]: Error 0x800705de: Failed to configure per-machine EXE package.
[0550:0E74][2015-07-23T09:11:45]: MUX: Installation size in bytes for package: silverlight5_DRT MaxAppDrive: 0 MaxSysDrive: 0 AppDrive: 0 SysDrive: 0
AND
[0F08:14A8][2015-07-23T09:16:16]: Applying execute package:
{312d9252-c71c-4c84-b171-f4ad46e22098}, action: Repair, path:
C:\ProgramData\Package
Cache{312d9252-c71c-4c84-b171-f4ad46e22098}\VS2012.4.exe, arguments:
'"C:\ProgramData\Package
Cache{312d9252-c71c-4c84-b171-f4ad46e22098}\VS2012.4.exe" -repair
-quiet -burn.related.patch' [0F08:14A8][2015-07-23T09:16:23]: Error 0x80048bc7: Process returned error: 0x80048bc7
[0F08:14A8][2015-07-23T09:16:23]: Error 0x80048bc7: Failed to execute
EXE package. [0550:0E74][2015-07-23T09:16:23]: Error 0x80048bc7:
Failed to configure per-machine EXE package.
Anybody knows what to do with this? The error is coming when I repair Windows Phone SDK 8.0
There was a post-VS2013 update for the Windows Phone 8.1 SDK, some odds that you don't have it installed since you did not need it before. The download location is here.
Getting error messages like "port is in use" when there's no obvious reason why it should be in use and seeing excessive download times is also a very strong selector for your installed anti-malware product getting in the way. No specific advice on how to configure it when we don't know what it might be. You definitely first want to try to temporarily disable it so you can identify it as the source of the problem.
I have no Idea of what is the issue, but creating a new solution and importing the existing projects into a new solution has solved all the issues regarding emulator and debugger an AgHost.
Seems like the upgrade function integrated in the solution did not work properly.
I have a SQL CLR project that deploys stored procs to a server. For 2 years I've always been able to just right click the project and deploy. Yesterday I have started to get errors when I try to do that. I was able to deploy a new version last week but not this week.
------ Build started: Project: '', Configuration: Debug Any CPU ------
'' -> E:\Development\Code\SqlDeployables\''\bin\Debug\''.dll
------ Deploy started: Project: '', Configuration: Debug Any CPU ------
Error: Class not registered.
Looking for object with CLSID: {475E0C1F-1E61-4197-9324-10A148C512F8}.
========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped ==========
========== Deploy: 0 succeeded, 0 failed, 0 skipped ==========
I've been searching around and can't find anything on the error. There has been no updates on the sql server since I could last deploy. I have uninstalled my VS2010 updates as well as .net updates on my machine and that has not done anything. The only updates I have not uninstalled were office ones, which I would think are not the problem.
Any ideas? I've tried resetting permissions on the sql machine. Removed Stored procs manually and redeploy. I've gone back to a previous version of the project and tried to deploy. Restarted SQL Server services on machine.
Visual Studio 2010
SQL Server 2008
Thanks
Somehow your visual studio install has gotten messed up. That CLSID points to the class Microsoft.VisualStudio.Data.Schema.Package.Sql.Internal.ManagedBuildLoggerComClass in the com object C:\Windows\system32\mscoree.dll.
I would recommend trying to do a repair install on visual studio and see if that fixes your issue.
I had the same problem, and I couldn't figure out how to solve it. I think it might have something to do w/ a side-by-side install of VS2012, but I am not sure.
As a workaround I wrote my own T-SQL deploy script. The project builds all right, and it outputs dlls all right. All that is missing is the database deploy (ie, the commands that VS runs against the database to actually deploy your types and methods to the server). In the project's bin folder you may find the .sql file that VS generates; you can use this as a template. The deploy script will end up looking something like this:
USE SomeDatabase
GO
IF OBJECT_ID('dbo.[SomeFunction]') IS NOT NULL DROP FUNCTION dbo.[SomeFunction]
IF EXISTS (SELECT * FROM sys.assemblies WHERE NAME = 'SomeAssembly') DROP ASSEMBLY [SomeAssembly]
GO
CREATE ASSEMBLY [SomeAssembly] AUTHORIZATION dbo
FROM '\path\to\your\dll'
WITH PERMISSION_SET = SAFE
GO
CREATE FUNCTION [dbo].[SomeFunction] ....
EXTERNAL NAME [SomeAssembly].[SomeAssembly.UserDefinedFunctions].[SomeMethod]
GO
Then deploy your stuff manually via SSMS.