I'm getting an error when I try to view the Azure Compute Emulator UI.
Steps:
Launch an Azure project to kick off the emulator.
Right click on Azure emulator icon and select "Show Compute Emulator UI"
This produces the error:
"This application has encountered an internal error and needs to be closed"
This has been working before but I haven't changed anything so does anyone know what could have started causing the error now? The Storage Emulator UI still seems to display OK.
I have the following environment:
Windows 8.0
Visual Studio 2012 Professional
Azure SDK 2.2
Create system variable and user variable in your system environment variables :_CSRUN_STATE_DIRECTORY with value like 'C:\TempAzure' (without commas). DO NOT LEAVE A SLASH AT THE END like 'C:\TempAzure\'.
Follow this link and do it and refresh your environment vars because compute emulator will not get them until refreshed.
Is there a command to refresh environment variables from the command prompt in Windows?
This was the solution which worked for me.
A hint how I got it :
1. Start your event viewer and your azure sdk command prompt with elevated privileges ( as administrator )
2. type csrun /devfabric:start
3. Go to event viewer and hit F5 and look for the error from DFService.exe. There should be 2-3 new errors and the first should be from DFService. Look at the description - it should contain something like :
Application: DFService.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ArgumentException
Stack:
at System.IO.Path.CheckInvalidPathChars(System.String, Boolean)
at System.IO.Path.NormalizePath(System.String, Boolean, Int32, Boolean)
at System.IO.Path.GetFullPath(System.String)
at Microsoft.ServiceHosting.Tools.DevelopmentFabric.Program.Main(System.String[])
The last row flashes the red lamp :)
Related
Since quite a while, I've been trying to run an Android app for the humanoid robot Pepper on Mac OS 10.13.6. In the past, there occurred many issues when I was trying to run a virtual device in combination with the Pepper Emulator. When I tried to run the emulator with Android SDK version 30 or 29, I was always receiving an error message that there were "NO_CERTIFICATES" to permit the installation of the app. After trying the option to generate a signed bundle in Android Studio, no change was happening.
After downgrading to Android SDK version 23, it was finally possible to run the robot viewer while installing and starting the app on the virtual tablet device without any crash occurring. However the app didn't crash at this point, the following error message appeared in the log histroy:
E/qi.path.sdklayout: Cannot create directory '"/mnt/sdcard/.config/qimessaging"' error was: boost::filesystem::create_directories: Permission denied: "/mnt/sdcard/.config"
E/qi.os: Unable to create file: ''
As soon as I call the robot to execute an animation by clicking a button on the tablet interface, the app crashes and the following lines are printed to the log:
enter image description here
I thought that this error might be implied by the first error message. Therefore I tried to update the AndroidManifest.xml with this permission tag:
enter image description here
Unfortunately, this did not change anything. So I hope to receive some help from your community. Also I would be extremly happy to receive some advice from you, #dfinn. I've read that you got around several issues to run a Pepper application on your Mac, is this correct?
Thanks a lot for all your support!
The error E/qi.path.sdklayout: Cannot create directory – Permission denied has no visible consequence.
The real issue you have here is the one described in the backtrace, java.lang.IllegalStateException: Could not execute method for android:onClick.
It looks like something is wrong with an onClick callback in your Android code.
I'm using Visual Studio 2019 to develop a .NET Core 3 application which runs on embedded Linux. I am able to build the code in Visual Studio 2019. If I copy the binaries manually to the Linux machine and then start the application running there then I am able to attach the Visual Studio debugger to the remote process over SSH in Linux and debug the application. This does work, but it's tedious to deploy it, start it and attach the debugger manually for each debug session. I do have a script in Visual Studio Code which works, but I want to use Visual Studio Professional.
I'm trying to write a Visual Studio Extension so that I can press a key in Visual Studio to have the application built, deployed, started and then connected to the debugger. I would then share the extension with my team. It's very nearly working, except for attaching the debugger.
In the extension I am able to list the processes running in the Linux machine and select my application using this code:
EnvDTE100.Debugger5 debugger = (EnvDTE100.Debugger5)dte.Debugger;
EnvDTE80.Transport transport = debugger.Transports.Item("SSH");
EnvDTE80.Engine engine = transport.Engines.Item("Managed (.NET Core for Unix)");
EnvDTE80.Process2 process = (EnvDTE80.Process2)debugger.GetProcesses(transport, "192.168.11.1").Item("app");
process.Attach2(debugger);
There are two problems:
The call to GetProcesses() opens a dialog where I need to enter the Linux username and press enter, how can I specify the username in code to avoid the dialog appearing?
Even though the selected process looks like the right one (process.ProcessID matches what I see in Linux if I run the ps command), I get an exception when I call Attach2(). The exception message is "Exception from HRESULT: 0x8971001E"
I feel like I'm really close to getting this to work, any suggestions for how to finish it?
I also solved the second problem by changing the parameter passed to Attach2() from debugger to engine, as shown below:
EnvDTE100.Debugger5 debugger = (EnvDTE100.Debugger5)dte.Debugger;
EnvDTE80.Transport transport = debugger.Transports.Item("SSH");
EnvDTE80.Engine engine = transport.Engines.Item("Managed (.NET Core for Unix)");
EnvDTE80.Process2 process = (EnvDTE80.Process2)debugger.GetProcesses(transport, "root#192.168.11.1").Item("app");
process.Attach2(engine);
I found out how to add the user Name, but not the Password:
In GetProcess(), set transportQualifier to $"{userName}#{hostName}".
The 1st time the Window will still Pop up and ask for the Password.
But after that VisualStudio has stored the connection including the password.
I have a web project, which works fine on local PC. But when I publish it on Azure Website, I get an error:
Could not load type 'Infrastructure.Asset.AssetContext' from assembly
'Infrastructure'. Description: An unhandled exception occurred during
the execution of the current web request. Please review the stack
trace for more information about the error and where it originated in
the code.
Exception Details: System.TypeLoadException: Could not load type
'Infrastructure.Asset.AssetContext' from assembly 'Infrastructure'.
where AssetContext is DbContext from another project inside solution. As I understand, this assembly is not published correctly on Azure. So, I removed all files on Azure Website via Kudu and republish again. The same. I try to connect to remote Db from my local - it works. I tried to rebuild solution, reopen Visual Studio etc. Nothing happened
Why it can be happened, what is wrong and how to fix?
There is a similar SO thread What could be causing a System.TypeLoadException in a Visual Studio Unit Test?, I think which answers are valuable for your current issue.
Please follow the figure below to get the information of what platform you used is on Azure Website, then to select the current mode in Visual Studio to build and publish.
why I am getting this error when I am trying to run my application in real device not simulator
ApplicationVerificationFailed: Failed to verify code signature of /private/var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.ttjwEf/extracted/DSP.IOS.app : 0xe8008016 (The executable was signed with invalid entitlements.)
error MT1006: Could not install the application '/Users/macbookpro/Documents/gitProject/DSPMobileGit/DSP.Mobile/DSP.iOS/DSP.IOS/bin/iPhone/Debug/device-builds/iphone6.2-9.3.5/DSP.IOS.app' on the device 'Mohamed’s iPhone': Your code signing/provisioning profiles are not correctly configured. Probably you have an entitlement not supported by your current provisioning profile, or your device is not part of the current provisioning profile. Please check the iOS Device Log for details (error: 0xe8008016).
here steps I did to run my app
First I created project in Xcode with same bundle name and let Xcode handle Provisioning
when I tried to run in Visual studio it dosent work
Second I create manual provisioning with wild id but it dosent work
I note something each time I set my signing identity and provisioning profile , when I back to screen I find it back to none again
may be that is the reason
Using Visual Studio for Mac 2019
First, determine whether the problem is entitlements. Find tab "Deploying to Device", and look at the full message starting with
"ApplicationVerificationFailed: Failed to verify code signature of ..."
Look for:
... The executable was signed with invalid entitlements.
In that case, see https://stackoverflow.com/a/43055084/199364.
The below answer is for the other likely situation:
... no valid provisioning found for this device.
On newer versions of Visual Studio for Mac + Xamarin iOS (or Xamarin Forms, deploying to iOS):
Connect the phone to Mac via USB cable.
Popup on phone, select "Trust" this computer.
In VS, Open Info.plist.
Make sure the "Application" tab is selected at the bottom of the pane.
Select "Automatic Provisioning".
Follow the instructions.
When successful, you'll see (below "Automatic Provisioning" radio button):
Apple ID: your-apple-id-email
Team: your-company-name-or-your-developer-name
(Green checkmark) Ready to deploy app to connected device.
IMPORTANT:
Even if you have previously setup Automatic Provisioning for a different device, you still need to open Info.plist / Application tab after attaching this new device. (After doing this once per device, you can switch which device is attached, without repeating.)
If Xcode has never seen the device before, it can take MINUTES before Xcode has validated it and attached it. See following paragraph if you'd rather see Xcode giving you a message about what its doing (and spinning a busy indicator). Won't be any faster, but is more obvious that something useful might be happening. (On older Xcodes, people have reported delays up to 10-15 minutes.)
If having trouble getting it to see your phone, google for instructions to open XCode and add your phone as a device known to XCode (XCode menu Windows / Devices and Simulators / Devices tab). That is, it may be easier to first get it working under XCode, then go back to VS, disconnect and reconnect the cable to phone, try instructions above again.
Using Visual Studio (Windows) 2022
Personally, I always FIRST get the phone|tablet recognized using XCode, connecting it to Mac. See instructions above.
Then:
Connect device to PC.
Automatic Provisioning is found in YourApp.iOS / Properties / iOS Bundle Signing.
Select Team.
if it works => "Automatic provisioning completed successfully."
OPTIONAL:
Disconnect device from PC, connect it to Mac - should be listed under "Remote Devices" in VS on Windows.
TBD: Not sure why I failed to get it to be listed as a Local Device, when it was attached to PC.
I had the same issue in a Xamarin.iOS project. I found a workaround. The reason was the update from Xamarin.Swift4 package 4.0.0.1 to 4.0.0.2.
After I downgraded back to 4.0.0.1 the issue no more exist.
I created an issue report at github: https://github.com/Flash3001/Xamarin.SwiftSupport/issues/25
I'm trying to add snap into Microsoft Management Console in windows 10. But when I try to add certificate, an error message is coming with the header Microsoft Management Console has stopped working:
When I click the Debug button, Visual Studio 2015 gives me a message like this:
I've tried a solution found by google search saying to run sfc/scannow command in command promt but didn't get any result.
So this doesn't address the error itself, but if you were trying to use the snap-in to access the local computer certificate store then there is a work around.
Open up command prompt and type in 'certlm.msc', this should directly open up the local computer certificate store plug-in without having to go through the buggy menus.