I am trying to get an install of ASP.Net DNX on Windows. I followed the instructions at: https://github.com/aspnet/home#cmd
The problem is. when I run this, I get an error stating:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\parsonsjm0818\Desktop>#powershell -NoProfile -ExecutionPolicy unrestric
ted -Command "&{$Branch='dev';iex ((new-object net.webclient).DownloadString('ht
tps://raw.githubusercontent.com/aspnet/Home/dev/dnvminstall.ps1'))}"
Using temporary directory: C:\Users\PARSON~1\AppData\Local\Temp\dnvminstall
Downloading DNVM.ps1 to
Downloading DNVM.cmd to
Installing DNVM
The script 'dnvm.ps1' cannot be run because it contained a "#requires" statemen
t at line 2 for Windows PowerShell version 3.0. The version required by the scr
ipt does not match the currently running version of Windows PowerShell version
2.0.
At line:1 char:191
+ [System.Threading.Thread]::CurrentThread.CurrentCulture = ''; [System.Threadi
ng.Thread]::CurrentThread.CurrentUICulture = '';$CmdPathFile='C:\Users\parsonsj
m0818\.dnx\temp-set-envvars.cmd';& <<<< 'C:\Users\PARSON~1\AppData\Local\Temp\
dnvminstall\dnvm.ps1' setup
+ CategoryInfo : ResourceUnavailable: (dnvm.ps1:String) [], Scrip
tRequiresException
+ FullyQualifiedErrorId : ScriptRequiresUnmatchedPSVersion
C:\Users\parsonsjm0818\Desktop>
Can I install the DNX with only Powershell 2.0 or do I have to upgrade to 3.0?
The script 'dnvm.ps1' cannot be run because it contained a "#requires" statemen
t at line 2 for Windows PowerShell version 3.0.
If you want to be sure that the script will work, you'll have to use Powershell v3.0. It is certainly possible to modify the script to remove the requirement, but it as probably put there for a good reason. It would just be a roll of the dice if it would actually work if the requirement was removed.
Related
I have debian 11 installed in wsl2 on windows 10. I use the dotnet cli tools in visual studio and cmd windows but much prefer the linux syntax. The sdk commands are not exposed to wsl apparently as I get "bash: command dotnet not found" errors. Because WSL is essentially mapping linux commands to windows I don't think I should be installing the dotnet sdk again for linux, but can't really find any confirmation of that. Anyone here doing this who can advise? Just don't want to have to maintain two sets of the dotnet sdk if WSL does not require it.
The sdk commands are not exposed to wsl apparently as I get "bash: command dotnet not found" errors.
That's because WSL does not run Windows executables - it is, after all, a Linux subsystem.
I don't think I should be installing the dotnet sdk again for linux
You have two choices:
Use the Windows subsystem (drop WSL),
install the Linux applications you want to run.
I have installed a fresh Windows10, and downloaded the "dotnet-install.ps1" from Microsoft:
https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet-install-script
And I ran it by:
powershell -Command "& '...\dotnet-install.ps1' -Channel 7.0 -Runtime windowsdesktop"
It returned success, and now if I rerun:
> .\dotnet-install.ps1 -Channel 7.0 -Runtime windowsdesktop
dotnet-install: Note that the intended use of this script is for Continuous Integration (CI) scenarios, where:
dotnet-install: - The SDK needs to be installed without user interaction and without admin rights.
dotnet-install: - The SDK installation doesn't need to persist across multiple CI runs.
dotnet-install: To set up a development environment or to run apps, use installers rather than this script. Visit https://dotnet.microsoft.com/download to get the installer.
dotnet-install: .NET Core Windows Desktop Runtime with version '7.0.2' is already installed.
dotnet-install: Adding to current process PATH: "C:\Users\daniel\AppData\Local\Microsoft\dotnet\". Note: This change will not be visible if PowerShell was run as a child process.
It says it's already installed.
However, when I try running my application:
Trying to run dotnet, but it's not found (neither from cmd, nor from powershell).
Tried rebooting the machine, then retry running this script, it keeps telling me it's installed, but I don't understand, what is going on.
I have done a clean install fuse on karaf at
C:\esb\redhatfusekaraf\fuse-karaf-7.8.0.fuse-780038-redhat-00001
FUSE_HOME environment variable is set to this directory.
I have OpenJDK installed at
C:\Program Files (x86)\AdoptOpenJDK\jdk-8.0.282.8-hotspot
PATH and JAVA_HOME are set properly and tested.
When I run fuse.bat from the above install here is what I get.
Microsoft Windows [Version 10.0.18363.1440]
(c) 2019 Microsoft Corporation. All rights reserved.
C:\Users\MO Tec>%FUSE_HOME%
'C:\esb\redhatfusekaraf\fuse-karaf-7.8.0.fuse-780038-redhat-00001' is not recognized as an internal or external command,
operable program or batch file.
C:\esb\redhatfusekaraf\fuse-karaf-7.8.0.fuse-780038-redhat-00001\bin>fuse
karaf.bat: Ignoring predefined value for KARAF_HOME
Red Hat Fuse starting up. Press Enter to open the shell now...
100% [========================================================================]
Karaf started in 2s. Bundle stats: 12 active, 13 total
No Fuse Shell. Anything else I can look at?
The problem was caused by a missing ">" in the maven settings.xml I discovered it trying to run an "mvn clean install" when maven crashed.
I fixed the missing ">" and not only did that command run and build success but the Fuse Console now appears.
I couldn't get Meteorite and Telescope running on windows 7, any ideas how should we do this?
Here's what I tried:
installed Meteor on win7 using win.meteor.com
tried to install Meteorite (following instructions on its Github page), but it threw
couple errors (although it finished installation):
C:\Users\Daler\AppData\Roaming\npm\node_modules\meteorite\node_modules\ddp\node_modules\w
s\build\bufferutil.vcxproj(18,3): error MSB4019: The imported project
"C:\Microsoft.Cpp.D efault.props" was not found. Confirm that the path
in the declaration is correct , and that the file exists on
disk.
C:\Users\Daler\AppData\Roaming\npm\node_modules\meteorite\node_modules\ddp\node_modules\w
s\build\validation.vcxproj(18,3): error MSB4019: The imported project
"C:\Microsoft.Cpp.D efault.props" was not found. Confirm that the path
in the declaration is correct , and that the file exists on
disk.
cloned Telescope, then ran it with mrt from its folder, but got errors about missing dependencies of Meteorite. manually copied "router" and "page-js" packages to "Meteor/packages" as suggested here:
But still, running mrt or mrt run exits without error.
However running with meteor command sometimes starts the server on localhost and then fails due to a missing file and sometimes cannot find/start MongoDB.
Installing Microsoft Visual C++ 2010 Service Pack 1 Compiler Update for the Windows SDK 7.1 (as suggested by https://github.com/TooTallNate/node-gyp) fixed the MSB4019 error for me doing npm install xxx on Windows7 x64.
The readme of that update states that the recommended order is
Visual Studio 2010
Windows SDK 7.1
Visual Studio 2010 SP1
Visual C++ 2010 SP1 Compiler Update for the Windows SDK 7.1
SQLite is available as
A complete VSIX package with an extension SDK and all other
components needed to use SQLite for application development with
Visual Studio 2012 targeting Windows Phone 8.0.
But I need to do some modification in source code.
Tim Heuer in his blog described how to build sqlite for WinRT.
The main part I guess:
Build the DLL:
nmake -f makefile.msc sqlite3.dll FOR_WINRT=1
If building for ARM:
nmake -f makefile.msc sqlite3.dll FOR_WINRT=1 OPTS=/DWINAPI_FAMILY=WINAPI_PARTITION_APP
What options should be specified to build for Windows Phone 8?
Update:
I've tried
nmake -f makefile.msc sqlite3.dll FOR_WINRT=1 OPTS=-DWINAPI_FAMILY=WINAPI_PARTITION_PHONE
Result:
Also I've tried
nmake -f makefile.msc sqlite3.dll FOR_WINRT=1 OPTS=-DWINAPI_FAMILY=WINAPI_FAMILY_PHONE_APP
Result:
Sqlite includes some tools to be built and run during the build process, i.e. on the platform you're building on: mkkeywordhash.exe and lemon.exe. These tools should be built by cl.exe targetting your build platform, not your target platform.
NCC variable is used to specify the location of native compiler:
nmake -f makefile.msc sqlite3.dll <your options> NCC="c:\Program Files\..path-to-native\cl.exe"
It might be enough. If another problem arises, find NCC in Makefile.msc and look around it for more information. E.g. you might have to set the following parameters:
XCOMPILE=1
USE_NATIVE_LIBPATHS=1
NCRTLIBPATH (where are your native CRT libraries?)
NSDKLIBPATH (where are your native SDK libraries?)