For local development purposes, I'd like to just run a .bat file to build my solution and run it on iis express.
Here's what I've got:
call "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Auxiliary\Build\vcvars32.bat"
devenv "C:\Path\To\Solution.sln" /build debug
echo "Web build completed. Launching IIS..."
CD "C:\Program Files (x86)\IIS Express\"
iisexpress /path:C:\Path\To\Webroot /port:58389 /clr:v4.0
This does indeed successfully build the solution and start iis express.
Here's my output:
[vcvarsall.bat] Environment initialized for: 'x86'
Microsoft Visual Studio 2017 Version 15.0.28010.2050.
Copyright (C) Microsoft Corp. All rights reserved.
1>------ Build started: Project: PDS.Utilities, Configuration: Debug Any CPU ------
2>------ Build started: Project: PDS.Ibex, Configuration: Debug Any CPU ------
...
========== Build: 11 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
"Web build completed. Launching IIS..."
Copied template config file 'C:\Program Files (x86)\IIS
Express\AppServer\applicationhost.config' to 'C:\Users\CXSVH9\AppData\Local\Temp\2\iisexpress\applicationhost2018116141435830.config'
Updated configuration file 'C:\Users\CXSVH9\AppData\Local\Temp\2\iisexpress\applicationhost2018116141435830.config' with given cmd line info.
Starting IIS Express ...
Successfully registered URL "http://localhost:58389/" for site "Development Web Site" application "/"
Registration completed
IIS Express is running.
Enter 'Q' to stop IIS Express
When I fire up localhost, I get the following output in Command Prompt:
Request started: "GET" http://localhost:58389/login.aspx
Request ended: http://localhost:58389/login.aspx with HTTP status 200.0
Request started: "GET" http://localhost:58389/login.aspx
Request ended: http://localhost:58389/login.aspx with HTTP status 200.0
200's. So, that's good.
But in the browser, I get the message: "Requested view is not available" (a message peculiar to my environment, I'd guess — I just started with this codebase).
Of course, if I start the project from inside Visual Studio, everything works fine. But, as a frontend dev, I'd rather skip that and just fire the project up with a script and use VS Code to edit my static files.
Any thoughts on why this is not loading assets from my web project?
The really frustrating thing is I had this working before, but accidentally deleted my original .bat file and can't get things sussed again.
UPDATE
When I clear cache in the browser, it does GET all my assets with 200's. But still, "Requested view is not available."
Let me somewhat sheepishly answer my own question: I needed to start an additional web service that our website depends upon. This was as simple as writing another batch file to start that web service using the same technique above, but changing the path and the port to their appropriate values.
I've updated Xamarin on Visual Studio 2017 and when I go to build an new Android App I created, it has the following error:
Starting runtime checks
Starting emulator Android_Accelerated_Nougat ...
1>------ Build started: Project: Phoneworld, Configuration: Debug Any CPU ------
C:\Program Files (x86)\Android\android-sdk\tools\emulator.EXE -partition-size 512 -no-boot-anim -avd Android_Accelerated_Nougat -prop monodroid.avdname=Android_Accelerated_Nougat
Could not launch 'C:\Program Files (x86)\Android\android-sdk\emulator/qemu/windows-x86_64/qemu-system-x86_64.exe': No such file or directory
The selected emulator couldn't be started. This can be caused by the process not having enough permissions. Please try to start VS as administrator, which can help to avoid it.
Emulator Android_Accelerated_Nougat cannot be started.
Runtime checks failed
To run an emulator in normal account that was created as administrator.
2 Steps:
Move 1 folder and 1 .ini file
Change paths values in 2 config files
First, move your emulator's .ini file and folder from admin's account.
Source - C:\Users\{admin account}.android\avd
Destination - C:\Users\{YOUR account}.android\avd
Second, change the emulator paths in 2 config files
Config file 1 - {emulator name}.ini
(1 key-value)
path
Config file 2 - {emulator folder}\hardware-qemu.ini
(4 key-value)
hw.sdCard.path
disk.cachePartition.path
disk.dataPartition.path
disk.encryptionKeyPartition.path
I suggest going doing the following in VS.
Navigate to: Tools > Android > Android SDK Manager and check that you have the correct tools installed for the Nougat android emulator you want to run.
I would say install the following under Android 7.0 - Nougat if not already installed.
Google APIs Intel x86 Atom System Image
Google APIs Intel x86 Atom _64 System Image
Once you have those installed, navigate to: Tools > Android > Android Device Manager.
Select the emulator in question and check what CPU/ABI you target and update it to use the new ones you installed in the previous step.
You should also try running your VS as Administrator, it could also help.
On a new installation of Windows 10 Enterprise Version 1703 I tried turning on the IIS feature, default options selected, via "Turn Windows features on or off," but ran into the error shown below:
I then attempted to install the feature using DISM. I opened an admin command prompt and entered:
Dism /Online /Enable-Feature /FeatureName:IIS-DefaultDocument /All
This should be the same as installing the default set of features for IIS. This also failed with the same error code 0x800f0922.
Lastly, I tried selecting IIS elements one piece at a time from the "Turn Windows features on and off" menu. This worked until I tried installing "HTTP Errors," which produced the window above again.
Running this command:
Dism /Online /Enable-Feature /FeatureName:IIS-HttpErrors /All
resulted in the same error.
How can I fix this?
Touch the file C:\inetpub\custerr\en-US\401-1.htm, creating any missing directories in the path, then run the installer again.
More info:
I viewed the log file for DISM located at C:\Windows\Logs\DISM\dism.log and found the following set of lines for the error:
2017-10-09 13:43:28, Error DISM DISM Package Manager: PID=4280 TID=14940 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f0922)
2017-10-09 13:43:28, Error DISM DISM Package Manager: PID=4280 TID=14940 Failed processing package changes with session options - CDISMPackageManager::ProcessChangesWithOptions(hr:0x800f0922)
2017-10-09 13:43:28, Error DISM DISM Package Manager: PID=4280 TID=14940 Failed ProcessChanges. - CPackageManagerCLIHandler::Private_ProcessFeatureChange(hr:0x800f0922)
2017-10-09 13:43:28, Error DISM DISM Package Manager: PID=4280 TID=14940 Failed while processing command enable-feature. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f0922)
2017-10-09 13:43:28, Info DISM DISM Package Manager: PID=4280 TID=14940 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
2017-10-09 13:43:28, Error DISM DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=800F0922
Following the recommendation, I checked the CBS log located at C:\Windows\Logs\CBS\CBS.log and found the following line with the same timestamp:
2017-10-09 13:43:28, Error CSI 00000096 (F) STATUS_OBJECT_PATH_NOT_FOUND #5294871# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile(flags = (AllowSharingViolation|AllowAccessDenied), handle = {provider=NULL, handle=0, name= ("null")}, da = (FILE_GENERIC_READ|DELETE|WRITE_DAC|WRITE_OWNER|FILE_WRITE_ATTRIBUTES|FILE_WRITE_EA|FILE_APPEND_DATA|FILE_WRITE_DATA|0x00000040), oa = #0x92431fdd18->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[38]'\??\C:\inetpub\custerr\en-US\401-1.htm'; a:(OBJ_CASE_INSENSITIVE)}, iosb = #0x92431fdd78, as = (null), fa = (FILE_ATTRIBUTE_NORMAL), sa = (FILE_SHARE_READ|FILE_SHARE_WRITE), cd = 5, co = (FILE_NON_DIRECTORY_FILE|FILE_SYNCHRONOUS_IO_NONALERT|0x00004000), eab = NULL, eal = 0, disp = Invalid)
I was able to determine that it was looking for the path C:\inetpub\custerr\en-US\401-1.htm and couldn't find it. Sure enough, that path did not exist at all.
First, I tried testing permissions by giving the user object Everyone full control access to inetpub. I know, not ideal, but it was worth it to test it. I ran that DISM command again to add HttpErrors, but still failed. Finally I just created the directories custerr and en-US, and a blank text file called 401-1.htm, and tried DISM one last time. The folder instantly populated with the rest of the HTTP error pages and the installation completed.
Hope this helps someone.
I had to uninstall Windows Process Activation Service feature first, reboot, then I was able to install IIS properly.
I created the two directory paths / empty files with no change. But - I had selected to install -only- IIS Metabase and IIS 6 configuration compatability. When I additionally selected to install the IIS Management Console the procedure successfully ran to completion.
Disabling McAfee solved the problem for me.
I had this error but was able to get IIS installed just by persevering with Control Panel | Programs | Turn Windows features on and off. When I first launched this, if I just selected the top-level Internet Information Services, as I've done with every other computer and every other version of Windows, I got this response repeatedly. With or without my antivirus running (which in my case is ZoneAlarm and MalwareBytes).
I got around this by expanding the IIS entry in the feature list, and just installing a few of the individual items at a time. My goal at the start of this was just to hone in on exactly what the problem was, although I found that every sub-component installed successfully.
Pros: everything installed OK, and only one of the subcomponents required me to reboot (and even that might have been because I also took the opportunity to get rid of IE11). And I suppose it's good that I didn't have to track down the actual MS error which caused this. Cons: there are probably 30-odd subcomponents nestling in three or four tiers under the main IIS option. Even though it all worked in the end, it took a couple of hours.
I got around this by expanding the IIS entry in the feature list, and installing each individual item at a time
I run into this error while trying to install Request Monitor feature of IIS. In order to troubleshoot it, I would recommend checking:
CBS logs (C:\Windows\Logs\CBS)
DISM logs (C:\Windows\Logs\DISM)
ApplicationHost.config file (C:\Windows\System32\inetsrv\config)
The output of Dism /Online /Cleanup-Image /ScanHealth command
Procmon logs (Use Process Monitor tool)
In my case Procmon logs showed PARSE_ERROR_INFO while reading applicationHost.config file which was corrupted. Reinstalling IIS solved the issue. Source: 0x800f0922 Update IIS-RequestMonitor of package IIS-WebServer-Core-Package failed
On Windows 10, version 1909, I had to first install the "IIS Management Console" feature.
Then I was able to add the features under the IIS 6 Management Compatibility folder without getting the 0x800f0922 error.
I was able to add both [IIS 6 Management Console] and [IIS Metabase and IIS 6 configuration compatibility] at the same time.
Then I was able to install the program that needed these as prerequisites, Exchange Management Console 2010 bayy-bee! Yey Yey.
I had the same problem in a Windows Server 2012 R2. In my case it solved after running all the pending updates on windows update (even the optional ones, it was one of them)
All config files in the IIS folder has to be present too
Location:
C:\Windows\System32\inetsrv\config\
I have created a Winform App to Run Coded UI test scripts recorded in VS2013. Its finely running in the VS2013[update 4] installed machine. But when try to run this in Test Agent 2013 installed machine, the exception has been thrown at Playback.Initialize() method , as "The following package failed to load: "C:\Program Files (x86)\Common Files\Microsoft Shared\VSTT\12.0\Microsoft.VisualStudio.TestTools.UITest.Extension.IE.dll"
I tried adding this dll in the reference but still the problem persists. I have added the following references. And I am sure that these dlls are available in the mentioned path.
Microsoft.VisualStudio.QualityTools.CodedUITestFramework.dll
Microsoft.VisualStudio.QualityTools.UnitTestFramework.dll
Microsoft.VisualStudio.TestTools.UITest.Common.dll
Microsoft.VisualStudio.TestTools.UITest.Extension.dll
Microsoft.VisualStudio.TestTools.UITest.Extension.IE.dll
Microsoft.VisualStudio.TestTools.UITest.Framework.dll
Microsoft.VisualStudio.TestTools.UITest.Playback.dll
Microsoft.VisualStudio.TestTools.UITesting.dll*
In that machine, only Test agent 2013 is installed and Configured for "Interactive Process" . Neither Test Controller is installed nor configured with any other test Controller installed machine.
I tried to Run the scripts with MStest using Command Line. Its running.
I have tried a lot by adding/removing many Coded UI dlls. But still the problem persists. Did I miss something? Thanks in advance.
We have a ssh based svn access. We were using the team city VS addin for remote runs without checking in post run as this failed due to the addin not supporting ssh pre version 6.5.
after upgrading to version 6.5 this has stopped working and has started giving us the following error -
Error while checking for incoming Subversion changes. svn: Can't create tunnel: The system cannot find the file specified..
Svn has exited with code '1'.
svn status
-even though we dont use post run commit!
Has anyone else had this issue!
BR
Niladri
Edit the file c:\Documents and Settings\<USER>\Application Data\Subversion\config
Locate the section named [tunnels]
Add the following line:
ssh=c:/path/to/plink.exe -i c:/path/to/your/key.ppk