Is it possible to install "Windows Phone Developer Tools RTW" on a machine without installing Visual Studio and Expression Blend?
The reason I am asking is that I want to install it on a build server.
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=04704acf-a63a-4f97-952c-8b51b34b00ce&displaylang=en
You can download and install the tools and then uninstall any options you don't require. Such as VS2010Express & Blend.
Unfortunately there isn't a better solution available at the moment.
Yes, that's exactly why downloads like the one you referenced exist - build servers, production servers have to build/run without Visual Studio.
Do you have specific needs here? I see the q is tagged for Windows Phone.
Online info about the Windows Phone developer tools seems to indicate that it's currently a bit of a work in progress. Don't see any obvious way to put this standalone on a build machine.
Related
I'm trying to install WinDbg from this page, just under the Debugging Tools for Windows 10 (WinDbg) section. However, when I download the executable and run it, it tells me that
You must uninstall the Windows Software Development Kit - Windows 10.0.10586.15 before you can install the latest version of the kit.
I'm guessing this probably has to do with the fact that I already have VS 2015 (and the Windows 10 SDK) installed. However, when I go to the Developer Command Prompt and type in
> where windbg
it tells me that it can't find WinDbg. How, then, do I install it without doing anything drastic (like reinstalling Visual Studio)?
I just ran into this same problem (with a slightly newer version of the SDK) when setting up a VM with Windows 10 and Visual Studio 2015. Following the general rule (or at least, what used to be the general rule), I installed Visual Studio first before attempting to install the SDK.
Even though I picked all the options in the Visual Studio install, and I appear to have gotten large portions of the SDK, I didn't get the debugging tools or the application verifier, which I wanted. The "Debuggers" folder was empty. Yet when I tried to download and install the standalone Windows 10 SDK, I got the error message you quote, that I needed to uninstall the SDK before I can install the latest version.
Microsoft's site is absolutely no help. It gives no clues about the appropriate way to install the software. Harry Johnston's comment got me going in the right direction.
After installing Visual Studio 2015, you already have the Windows 10 SDK. You do not need to download it separately. To get the additional tools on Windows 10:
Open Settings → System → "Apps and features".
Scroll down to "Windows Software Development Kit".
(I had two versions of it installed. The top one was newer. I'd recommend that you proceed with the newer version for the following steps.)
Select it, and click "Modify". Then, because it's Windows 10 and everything is harder than it needs to be, click "Modify" again.
The installer will launch. Select the "Change" option, and click "Next".
Place a check next to the additional features/tools you want, click "Change" to start the process.
After waiting some time, it will have downloaded and installed the additional portions of the SDK. You should now be good to go!
(This does seem like a bug in my case. The two versions of the SDK (the one I have installed and the one whose installer I downloaded) are identical (both are for version 10.0.10586.212), so running the standalone installer should just launch the same setup tool that you are able to launch from Settings, enabling me to Change/Remove Features. Oh well, at least this works.)
I have a small WP app and I need to show a (interactive) demo of it and show its features, to another person who doesn't have any WP-related software installed on his PC.
Is there a super lite version of the WP emulator that the other person can download?
Also, how can I create an installation file of the WP app so that it would be easy for him to install & run ?
Surely he won't need to install the whole SDK, including Visual Studio, right?
To run the emulator you'll need to install the full SDK (http://dev.windowsphone.com/en-us/downloadsdk) but note that this doesn't require an existing version of Visual Studio.
There is no stand alone installer for just the emulator.
Apps are compiled into XAP files (similar to APK) and the Application Deployment application (installed as part of the SDK) will allow this to be loaded into the emulator. This tool can also be used to load the app into attached, developer unlocked, devices.
In terms of demonstrating an app to someone not familiar with Windows Phone, I've found that getting them to experience it on an emulator is often a sub-par experience and doesn't create the best experience. It's far better to get people to experience applications on actual devices. Alternatively, if it's very early in the application's development it's often better just to capture a video of the application running (from the emulator if fine and normally easier).
He would need to install VS Express with all the requirements that needs (Win8, CPU support for Client Hyper-V).
Emulator works pretty well over Remote Desktop and other remote viewing tech such as Skype, so that's another option.
Ok, i think i've found the needed steps:
send the XAP file from "Documents\Visual Studio 2010\Projects\AppName\Bin\Release\" where "AppName" is the name of the app.
download and install the sdk . not sure if Visual studio is needed.
run "XapDeploy.exe" tool which will allow to run the emulator and install the XAP file into it.
The file is somewhere similar to :
C:\Program Files (x86)\Microsoft SDKs\Windows Phone\v8.0\Tools\XAP Deployment
run the app from within the emulator.
Since Microsoft is no longer supporting one of the most useful tools ever, apparently we are left to fend for ourselves. Has anyone been able to get the Web Application Stress Tool (WAST) to install on their Windows 7 machine?
I found this link (albeit in Italian) to download the Homer setup program:
http://www.maurodalfreddo.it/archives/89/web-application-stress-tool-anche-su-xp
Visual Studio Team System (VSTS) is better option.
http://msdn.microsoft.com/en-us/library/ms182561(v=vs.90)
I am interested in windows mobile7 application development and struggling with setting up the development environment. I found this DISCUSSED LINK.
(So it answered one problem that I had. I have already installed VS2010 Ultimate edition. I guess when I install Windows mobile7 SDK, it will install all the Windows mobile7 SDK tools without affecting the VS2010 that I have already Installed)
In my laptop I have windows7 64Bit operating system. Can someone please send me the steps that I should follow to make the environment to start windows mobile7 application development without affecting existing VS2010.
If someone can post the steps in sequence (including where I can find the SDK tools), Highly appreciated. Thanks inadvance...!!!
You can't install Windows Phone tools without affecting existing VS2010 installation. How would you create Phone apps without adding phone tools to the existing installation? Adding tools is an affect, is it not? Why worry about adding more tools? It's not going to take anything away from VS.
Download the tools from create.msdn.com. Run the Windows Phone tools, and start writing phone apps. It really is that simple. As for the tools installing the express version, I don't think so. I have ultimate, and looking through my file system now, there is only one devenv.exe, not a second one for express.
I'm having a problem on my TeamCity CI build server where during compilation I get the following error:
C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(2342, 9): error MSB3086: Task could not find "AL.exe" using the SdkToolsPath "" or the registry key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SDKs\Windows\v7.0A". Make sure the SdkToolsPath is set and the tool exists in the correct processor specific location under the SdkToolsPath and that the Microsoft Windows SDK is installed
I've found similar reports from a year ago when people were upgrading to .NET 3.5, for example this one. In that case, installing the latest SDK solved the issue, however I have already installed the latest SDK (Microsoft Windows SDK for Windows 7 and .NET Framework 4) on my build server. The MSBuild tools are all there on the server, in a folder called
C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319
and AL.exe exists in
C:\Program Files\Microsoft SDKs\Windows\v7.1\Bin\NETFX 4.0 Tools
However the registry key mentioned in the error message does not exist. So, it seems like there is something wrong with the installation/configuration of MSBuild. This error only happens for projects that have embedded resources, which require AL.exe.
As you have install the latest SDK (I'm assuming that's v7.1)
Go to "Microsoft Windows SDK v7.1" from the Start menu
Select "Windows SDK 7.1 Command Prompt" and enter
cd Setup
WindowsSdkVer -version:v7.1
This will tell msbuild to use that version of the tools without needing to do any scary registry editing.
Even though the question is quite old but it still appears in the top of google search results so I decided to post my solution as well. I have trapped into same issue while during TeamCity setup on Windows Server 2016 and Windows 10 Pro.
I have installed Microsoft Build Tools 2015 and Windows 10 SDK (Only tools for .NET 4.6.2) and got the error from question.
The missing puzzle was to set environment variable: TargetFrameworkSDKToolsDirectory=C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.6.2 Tools.
After setting environment variable MSBuild was able to resolve all needed tools including AL.exe and build succeeded.
Please let me know if same can be achieved by setting values in registry, but otherwise environment variables also works very well in this case and no installation of VS is needed.
You also need to apply the following registry fix to update msbuild to point to the V7.1 sdk values.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions\4.0]
"MSBuildToolsPath"="C:\\WINDOWS\\Microsoft.NET\\Framework\\v4.0.30319\\"
"MSBuildToolsRoot"="C:\\WINDOWS\\Microsoft.NET\\Framework\\"
"FrameworkSDKRoot"="$(Registry:HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Microsoft SDKs\\Windows\\v7.1#InstallationFolder)"
"MSBuildRuntimeVersion"="4.0.30319"
"SDK40ToolsPath"="$(Registry:HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Microsoft SDKs\\Windows\\v7.1\\WinSDK-NetFx40Tools-x86#InstallationFolder)"
"SDK35ToolsPath"="$(Registry:HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Microsoft SDKs\\Windows\\v7.1\\WinSDKNetFx35Tools#InstallationFolder)"
"MSBuildToolsPath32"="$(Registry:HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\MSBuild\\ToolsVersions\\4.0#MSBuildToolsPath)"
I had the same problem there, here's my simple answer to this.
After you have installed the Microsoft Windows SDK 7.1 on the TeamCity Server.
In Regedit Change this key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions\4.0\SDK40ToolsPath
to
$(Registry:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SDKs\Windows\v7.1\WinSDK-NetFx40Tools-x86#InstallationFolder)
Follow the below steps. This worked perfectly to me. Saved my time.
1- Right-click the My Computer icon and choose Properties, or in Windows Control Panel, choose System.
2- Choose Advanced system settings.
3- On the Advanced tab, click Environment Variables.
4- Click New to create a new environment variable under User variable section.
5- Variable name: TargetFrameworkSDKToolsDirectory
6- Variable value: TargetFrameworkSDKToolsDirectory=C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.6.2 Tools
Variable value depends on your SDK installation path.
7- Click OK and Save all windows.
8- Restart Visual Studio.
I have a simple, effective fix.
The problem seems to be that the tools version delivered with Visual Studio is version 7.0A, while the version delivered with the Windows SDK is version 7.1. That's all very well, but MSBuild.exe is still looking for the version 7.0A registry keys, which don't exist. This has to be a bug!
Looking in my registry, all the information for V6.0 and V7.1 is present and correct. So my solution is simple. I created a registry link that makes an alias of the 7.1 keys.
It's not possible to create registry links using the built-in tools, so I downloaded a little utility called 'regln' from here.
C:>regln-x86.exe "\Registry\Machine\SOFTWARE\Microsoft\Microsoft SDKs\Windows\v7.0A" "\Registry
\Machine\SOFTWARE\Microsoft\Microsoft SDKs\Windows\v7.1"
Job done. MSBuild now works perfectly on the TeamCity server.
Add a system env variable TargetFrameworkSDKToolsDirectory
like this:
TargetFrameworkSDKToolsDirectory=C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.6.2 Tools
restart VS
Ran into the same issue setting up a new build server on Windows 10.
Found and installed the latest (at the time) Microsoft Windows SDK for Windows 7 and .NET Framework 4 and that solved the problem.
We recently had this problem trying to get our .Net 4.0 builds working. We found that the location of al.exe had changed between where the original MSBuild that came with .Net 4.0 looks, and the Visual Studio SDK for .Net 4.0 (which was released later).
Since the only standalone installation of the SDK tools available is the one we had already installed without success (the one you mentioned), the only solution we could think of was to install Visual Studio on the build agents. We put Visual Studio 2010 Express (to keep the installation as lightweight as possible) on there and the problem went away. Not a pretty solution, but it did work - installing VS2010 also installs the SDK tools of the specific version that MSBuild appears to be looking for.
This is a problem that really shouldn't happen, but there didn't seem to be a way of making MSBuild look in the correct place for the tools, even hacking around in the registry.