I just installed the Windows Phone 7.1 SDK + 7.1.1 Update on a freshly installed Windows 7. The installation of 7.1 SDK went fine, during applying the 7.1.1 update, my VM freezed and it took me some back and forth to get system booting again, using the MS recovery during startup. I then re-applied the 7.1.1 update.
Now, after starting VS Express and creating a new project, I'm unable to select a target for testing my application, the drop down menu is just empty (this happens to newly created projects and existing ones).
Any hints what might be wrong?
Related
I'm creating a windows desktop universal app (UWP) using Windows Template Studio on Visual Studio 2019 Community, on a Windows 10 Family Edition.
Windows and VS2019 were updated today (before creating this app).
After the project was created using WTS i have an error telling me (mine is in french so i'll try my best to translate) that : I need to upgrade to "windows 10, version 2004 (10.0.19041.0)" in order to display this content (aka : the XAML UI designer). However, the 19041 sdk is already installed. I can build and run the application just fine. It only a problem with the designer.
If i change the application property target to from 19041 to version 1903 (10.0 ; Build 18362) and reload the project, it works just fine.
I don't think i really need this 19041 (i hope so) but : what's happening and how to fix it ?
If you set the target version at 19041 (2004), this requires your development environment to be at least 19041. The SDK installed through Visual Studio contains some development tools corresponding to the platform, but UWP development usually requires some native resources (such as colors, control styles, etc.), and these resources will follow the system update.
So when you set the target version of the project to 19041, the target of some local resources referenced by the project is 19041. If your development environment is lower than this version, the designer will not be able to display.
When I try to create a new Windows 10 UWP, or open or build existing samples or projects, I get the following error:
The imported project "C:\Program Files
(x86)\MSBuild\Microsoft\WindowsXaml\v14.0\8.2\Microsoft.Windows.UI.Xaml.CSharp.targets"
was not found. Confirm that the path in the declaration is correct,
and that the file exists on disk
I am running VS2015 Enterprise on Windows 10 Pro. Windows 10 SDK (10240) and Emulators installed. Have re-installed VS2015 several times without luck. There is no v14.0\8.2 folder on my machine. Tried to copy the v14.0\8.1 folder to create v14.0\8.2 folder but this only allows you to load the project or create new ones, but build fails. This is driving me crazy.
Note: An earlier install of same VS2015 ISO and SDK on Windows 10 Enterprise Evaluation was running successfully until I had to re-format a few days ago when I upgraded my Windows 7 to Windows 10 Pro. I have now also tried to install a clean copy of Windows 10 Enterprise, re-install VS2015 with SDK and emulators, and yet no luck. Same error keeps repeating.
Any suggestions on where/how to create the v14.0\8.2 folder would be appreciated.
The solution is to navigate to Control Panel | Uninstall a program and to select Visual Studio 2015. This allows you modify you existing Visual Studio 2015 installation. When you install, it is recommended to select the "install all" features which added the templates.
This blog should be helpful for you.
Besides, what's the exact version of VS2015 and Win10 you installed?
Long time reader first time poster here.
I'm a Linux developer trying to get started on Windows development in my new job. I knew it would not be trivial but the first thing I'm trying to do is complete and integrate a netvmini port driver (started by a co-op student) into one of their C++ apps. I am struggling to get the build environment going...
The project was started in Visual Studio 2013 with a Windows 7 target. When I now open it in Visual Studio 2015 and try to build the solution I get:
"Unknown or unsupported property value Win7 for TargetVersion"
for each project. This also happens if I set the configuration to Win8 (both release and debug). If I set it to Win 8.1 I get:
"An SDK corresponding to WDK version '8.1' was not found. Please install the SDK before building"
I have installed every WDK and SDK I can lay my hands on from Windows 7 to Windows 10 using both the web and the VS2015 installer. I have even installed Visual Studio 2013 again but I can't even seem to get the WDK to integrate with that.
The end goal here is to be able to build this (and hopefully debug remotely in kernel mode) from my Windows 10/VS2015 workstation for targets from Windows 7-10. Any advice or documentation that details how to integrate new build platforms into VS would be helpful (all the MS documentation just tells me what I can do if I install this or that, but not HOW to do it)
I also had the same problem after running the Project Upgrade tool.
I discovered when making new configurations that "Win7" and "Win8" TargetVersion are now "Windows7" and "Windows8".
The upgrade tool does not make that change for you but I was able to manually edit my upgraded project with those changes and got it to build for all targets.
I discovered that the installer doesn't install the windows 10 SDK by default. So all the installing of other SDK's was useless. I Also found out that by installing the Win 10 SDK through the VS 2015 installer it integrates and allows me to build for targets back to windows 7 in VS 2015.
I've just installed the April 2015 release of the Azure SDK. It is version 2.6 and previously I was on 2.5. Now one of my projects will not load. It is the shared project in a Windows Universal application.
When I right-click the project and choose 'reload' I get the pop-up error
The method or operation is not implemented
The output window gives more detail:
Things.Shared.shproj : error : The composition produced a single
composition error. The root cause is provided below. Review the
CompositionException.Errors property for more detailed information.
1) No exports were found that match the constraint:
ContractName Microsoft.VisualStudio.ProjectSystem.References.IBuildDependencyProjectReferencesService
RequiredTypeIdentity Microsoft.VisualStudio.ProjectSystem.References.IBuildDependencyProjectReferencesService
Resulting in: Cannot set import
'Microsoft.VisualStudio.Azure.Deployment.ProjectReferenceMaintenanceService.ProjectReferencesService
(ContractName="Microsoft.VisualStudio.ProjectSystem.References.IBuildDependencyProjectReferencesService")'
on part
'Microsoft.VisualStudio.Azure.Deployment.ProjectReferenceMaintenanceService'.
Element:
Microsoft.VisualStudio.Azure.Deployment.ProjectReferenceMaintenanceService.ProjectReferencesService
(ContractName="Microsoft.VisualStudio.ProjectSystem.References.IBuildDependencyProjectReferencesService")
--> Microsoft.VisualStudio.Azure.Deployment.ProjectReferenceMaintenanceService
Resulting in: Cannot get export
'Microsoft.VisualStudio.Azure.Deployment.ProjectReferenceMaintenanceService.WireUp
(ContractName="Microsoft.VisualStudio.ProjectSystem.ConfiguredProject.AutoLoad")'
from part
'Microsoft.VisualStudio.Azure.Deployment.ProjectReferenceMaintenanceService'.
Element:
Microsoft.VisualStudio.Azure.Deployment.ProjectReferenceMaintenanceService.WireUp
(ContractName="Microsoft.VisualStudio.ProjectSystem.ConfiguredProject.AutoLoad")
--> Microsoft.VisualStudio.Azure.Deployment.ProjectReferenceMaintenanceService
The other parts to the Windows Universal app (the Windows 8.1 project and the Windows Phone 8.1 project) have two Azure NuGet packages installed: Windows Azure Mobile Services 1.3.2 and Windows Azure Storage 4.3.0. (N.B. Those two projects load without issue.)
This is not a show stopper for me since uninstalling the Azure SDK 2.6 removes the load failure. To uninstall I go via the Control Panel to 'uninstall or change a program' and then uninstall Microsoft Azure Tools for Microsoft Visual Studio 2013 - v2.6
I would like to know how to fix this without uninstalling the Azure SDK 4.6.
Over on the Azure Mobile Services forum Chuck Weininger has posted the following answer:
The [fixed] build of Azure SDK 2.6 is now available, but it may not have
propagated to all download servers yet.
You can run the Web Platform Installer and if you don’t have the new
build installed, it should allow you to install 2.6 again. But it
might not if you are accessing a download server that doesn’t have the
new bits yet. If WebPI doesn't allow you to install 2.6 again, then
wait a few hours and try again.
The build number for the version with the fixes is build
2.6.30508.1601. You can identify the build of the SDK from Control Panel -> Programs and Features -> Microsoft Azure Tools for Microsoft
Visual Studio 2013 – v 2.6. The Version column will display the build
number
I have followed Chuck's instructions and have the new build and the shared project now loads without issue.
We have been able to reproduce the issue, but don't have a workaround at this time. If you want to use the Universal App projects with VS 2013, you will have to uninstall Azure SDK for VS 2.6. The issue does not happen on VS 2015 RC if you would like to give that a try. We hope to have news soon about how we can get a fix for this issue on VS 2013.
Chuck Weininger, Dev Lead, Microsoft
https://social.msdn.microsoft.com/Forums/en-US/e8123821-dcb1-477f-a746-f6f016a724ea/cannot-load-shared-project-in-windows-universal-app-after-upgrading-to-azure-sdk-26?forum=azuremobile&prof=required#de621720-3afc-458c-ba85-f691be9e74c1
I am working with Eclipse Kepler 4.3.2 and latest Worklight Studio downloaded and installed through Eclipse Marketplace (6.2.0.00-20140801-1709).
There are a lot of official IBM docs and web pages stating that WL 6.2 supports Win 8.1 hybrid store app development. At the same time, the IBM tutorials lead to complete the build cycle using MS Visual Studio 12 Express.
As long as I know, VS 12 targets Win 8 only, so VS 13 is needed to target Win 8.1 store apps.
So, after creating a new hybrid app, I add the Window 8 desktop and tablet environment (and the JSONStore optional feature also), then build that environment. At this point I use VS 2013 to open the .jsproj located in the windows8/native folder. VS 2013 notifies that the project must be retargeted from Windows 8 to Windows 8.1, then asks confirmation to make writable two read-only files: index.html and cordova.js. The reason for changing the content of these files during the migration from Win 8 to Win 8.1 is to change several references from "Microsoft.WINJS.1.0" to "Microsoft.WINJS.2.0".
At this point the Visual Studio project is fully functional, and also correctly runs on the Windows 8.1 tablet simulator. The noisy problem is that at every build of the windows8 environment Worklight regenerates index.html and cordova.js adding again the references to WinJS.1.0.
So, the question is: does the current Worlkight Studio version full supports Windows 8.1 development? Or, there is something wrong in my approach?
Worklight Studio is certified to work on Windows 8.1 using Visual Studio 2013.
From reading your question, and specificically this part:
At this point the Visual Studio project is fully functional, and also
correctly runs on the Windows 8.1 tablet simulator. The noisy problem
is that at every build of the windows8 environment Worklight
regenerates index.html and cordova.js adding again the references to
WinJS.1.0.
What I think is going on here is this:
You are creating your project in Worklight Studio and then open it in VS13 which then asks to migrate WinJS 1.0 to 2.0 and everything is working for you.
What you then do is re-build your project in Worklight Studio which brings back WinJS 1.0 as well as index.html
If you do changes in Visual Studio but do not bring them back into Eclipse, then your changes from VS will be lost. That is expected, because you are working with 2 IDEs, so you need to make sure that you copy back your code.
The template for a Windows8 app from Worklight Studio seems to be generating WinJS 1.0 regardless of targetting VS12 or VS13
So the only issue here is 2 above. It is worth investigating and it will be.
As for a "workaround", as long as you properly manage your code in 1, 2 should not prevent anything as you will still be given the option in VS to migrate to WinJS 2.0; it's an annoynace, though.