I try to send an update for my app to Windows Store by Windows Dev Center Dashboard, this update contains 3 packages: 2 for Windows 8.1 (Desktop and Phone) as a bundle and 1 for Windows 8.0 that does not support any bundle.
Before the new dashboard the package for Windows 8.0 was accepted too in this configuration... not now and it reports this error:
A previous submission for this app was released with a Windows Phone 8.1 appxbundle. Subsequent submissions must continue to contain a Windows Phone 8.1 appxbundle.
but it isn’t a Phone package and for Windows 8.0 I can’t make a bundle! there is a solution? with the old dashboard that worked great.
Best regards,
Claudio
Not sure if it is applicable here. But in my case I've got the same error when updating UWP version of the application on the store where I had UWP, WP81 and W8.1 apps. The error was signaling the fact that the existent store UWP package was build with as a bundle but the new package was not.
So the solution was to replace in .csproj the <AppxBundle>Never</AppxBundle> with <AppxBundle>Always</AppxBundle>. If you publish from Visual studio directly you can do that from UI as described here.
I had this problem. I deleted all the files in the folder where the package is building to the store. Then I created a package for store. This problem is solved.
I had the same error message appearing from nothing (just making a new build, no changes to platform). When I checked the box "do not automatically increment" (in UI, lead to <AppxAutoIncrementPackageRevision>False</AppxAutoIncrementPackageRevision> in csproj) and filled in my own number, the package that came out was called:
1.3.0.0_AnyCPU_bundle.appxupload
If I did not do it it looked like:
1.3.0.17_AnyCPU.appxupload
The latter did not work for some reason. So setting own build number fixed this particular problem for me. Why it fixed it? No clue.
Related
This C++/WinRT announcement states "What this also means is that you no longer need to wait for us to update GitHub following the release of a new Windows SDK. Indeed, we will no longer be publishing the updated headers on GitHub at all since you can get them directly from the Windows SDK."
However if one delves one click further one finds that the "Windows 10 Preview Build of the SDK [is] to be used in conjunction with Windows 10 Insider Preview (Build 17025 or greater)" and "Installation on an operating system that is not a Windows 10 Insider Preview build is not supported and may fail."
Right now must one install a Windows Insider Preview of Windows 10? This is either a scary and lengthy process or straight impossible depending on one's admin rights.
Or can one grab the SDK and use the C++/WinRT bits on a box with a standard Windows 10 build?
Is the easiest route for some aspects of the C++/WinRT toolchain still GitHub?
How about if one is developing on a non-Windows-10 box, e.g. Windows 7? Zillions of commercial developers are in this situation and aren't in control of that.
Will the situation change and if so when?
Going forward does one wait for periodic updates to SDK previews, and if so how does one consume them?
Preview versions of the Windows SDK will not install on a non-Insider build of Windows. This is a restriction of the Windows SDK and not specific to C++/WinRT. In the long run (once RS4 ships) this won’t be a problem since you’ll be able to install the final Windows SDK for RS4 without this restriction.
In the short term, you need an Insider build of Windows to install the SDK, but you can then use that to target previous versions of Windows. I’m not sure whether it would work on Windows 7, but I don’t think that any developer using C++/WinRT would care to use Windows 7 when the Windows Runtime isn’t even available on that version of Windows at all.
The cppwinrt.exe compiler also relies on Windows 10 APIs to function. While this isn’t a dependency of code built with C++/WinRT, it is a requirement for building C++/WinRT components. Of course, the resulting binaries can then be executed on older versions of Windows, provided you handle light-up in the usual ways, such as with delay-loading.
Sorry if this is not suitable place to post it.
I have completed my program and already build it. it has no problem running on my laptop but when i run on other laptop, there is an error appear
To run this application you must first install one of the following version of
.NET framework: v4.0.xxxxx
Contact your application publisher about obtaining the appropriate version of .Net framework
How do i check my program using which kind of .Net framework for running the program? can i just disable it?
You need to download and install the .Net Framework on your other laptop.
If you have an installation project, you can have this happen automatically when the application is installed on another computer.
I am currently developing a Windows Store App that will eventually be targeted at the ARM devices when they are available. For now, I have been developing and testing from Visual Studio on my desktop computer and everything works fine. However, when I try to create an app package that I can pass along to others within my company for testing purposes, the application will not run properly.
The solution includes two projects. The first is a C++ project that is set to build a dll file. The purpose for this is to expose the Direct2D and DirectWrite libraries that seem to be unaccessible to a C# project. The second project is the C# project that references this dll for drawing functions and includes a XAML interface and most of the program logic. All of this works flawlessly on my development machine from within Visual Studio (and also when installing the package).
When I send the package files to other individuals within the company, the installation appears to work fine by installing with the PowerShell script. The tile appears in the start screen and the program will launch for a few seconds. The C# and XAML interface appears, but the DirectX portion of the application is not visible and the entire application shuts down within a few seconds. This makes me believe that the dll may not be installing or referenced correctly upon installation. I have checked the package file, and the dll file is included in the package after the build process is complete.
I have packaged a few different test programs (MSDN Samples) that have all installed on their machines, but we get the same results that they will not run (again, all samples run fine on my development machine when building them). The only test project that worked properly was a simple C# project that did not use DirectX at all. Any of the DirectX samples that I tried have all failed (including the native C++ samples that do not use C# at all).
To be clear, the process I use for building is going to Project -> Store -> Create App Packages and choosing the No option for uploading to the Windows Store.
Does anyone have any ideas on what might be going wrong with the build or installation process?
Thanks in advance for any help!
Does it work with the Metro Sideloader? I am not sure if it just adds a UI to the Powershell script, but it works for my team and me for testing...
Good luck!
Are you side loading a Debug version of your DirectX app onto a machine that does not have the Windows SDK installed? Visual Studio's default DirectX projects and the samples on MSDN both request the D3D11_CREATE_DEVICE_DEBUG flag when creating the D3D Device. Device creation will fail if the Windows SDK is not installed on the machine running the code.
Here are a few different options that will allow you to unblock yourself. Any one of these should give you the desired result:
Create a Release package and deploy that instead of a Debug package.
or - Go to DirectXBase.cpp and remove the D3D11_CREATE_DEVICE_DEBUG flag from the code.
or - Install the Remote Debugging tools for Visual Studio on the target machines. This will install the necessary SDK components to allow creation of D3D Debug devices. The other cool thing about this option is that once you're set up you won't have to create packages manually and side load them anymore. Just tell Visual Studio the name of your ARM machine and press F5 to deploy it remotely. More information here: http://msdn.microsoft.com/en-us/library/vstudio/bt727f1t.aspx
How are you deploying the native DLL with your project? Are you using project-to-project references? Can you verify that your DLL is ending up in the final package, in the root of the package application directory?
I recommend using Sysinternals Procmon to watch your application load on the target machine. If it crashes or fails, you can look in the log history for which DLL it is trying to load and failing. Typically this will show up as a repeated series of DLL load probes (it will try and load the dll from the application directory, and then proceed to try a number of other paths).
I am trying to open silverlight project. It has 12 projects inside.last two projects does not load properly. i am trying to reload those two project a pop up window opened and that is asking download silverlight runtime(silverlight developer.exe). while downloading this software it is giving error message : A 64 bit version of silverlight is already installed.
I closed visual studio i reopned same project again last two projects not loadded properly.
Can you please give me any suggestions why i am getting issue.
I think you developed the application in old version of silverlight. And you laptop/computer has now the latest version.
OR
You have corrupted silverlight runtime. So remove the current installation and re-install silverlight runtime again.
I added a web service consumer to a vb 2005 Windows app and tried to install it on another computer, which had an earlier version already installed (ClickOnce deployment). An error came up saying I needed to install Microsoft.SqlServer.PipelineHost in the GAC. I added PipelineHost to the list of references and marked it Copy Local = true, rebuilt the solution, published it and tried to install it on that other computer.
This time it said I needed to install Microsoft.SqlServer.DtsMsg, however, that component does not show up on my list of .Net components.
Where do I go from here?
Thank you.
The answer was to find the item in the Application Files list and to force Include them in the package.