I am trying to run the Q# Teleportation sample. I cloned from the official Microsoft GitHub Repository, restored all dependencies, I have the Q# Development SDK installed also. The problem is when i run it the first time it worked now i tried running it again and i get this error.
TeleportClassicalMessage' does not exist in the current context. I run it for the last time and it worked even with the Error. I have by the way set up TeleportationSampleas my startup project.Is there any reason for this behaviour?. I am new to Q#
Even with the red Squiggly the Application run after another try.
I solved this by deleted the bin and obj directories then run again.
my experience: Quantum Program The name 'BellTest' does not exist in the current context
From my experience (playing with slightly modified sample BellTest code), Q#-generated classes are properly referenced in C# only after you rebuild project (meaning dotnet build). So if you make some changes in names that are visible on the C# side, try building it and reference issues should go away.
This was tested using VSCode on Windows 10 x64, .NET Core v 2.1.103
When copy a Kony project from another mac laptop to my mac laptop and trying to open the properties window it doesn't appear at all, shall edit/remove any xml files?
Yes, copying the physical folder directly doesn't work sometimes. It may happen due to visualizer version mismatch.
You need to use File -> Export option from the existing machine. It creates a .zip file with you project contents.
enter image description here
Use File -> import option in the new machine to import the project.
Note: Project created using lower version of Kony Visualizer can be imported into higher versions. But the reverse is not possible.
e.g. Project created using Kony Visualizer 7.2 cannot be opened in 7.1 or 7.0 versions.
Hope this helps!
Don't just copy and paste the code. That won't work because of the underlying configuration files of each installation. Instead
Go to File>Export on your source workstation. This will generate a zip file for you.
Then copy that zip file to the target workstation.
In your target workstation go to File>Import.
You'll find that this works nicely and you won't have this issue.
Hope this helps.
Go to root folder of your project.
Zip it and move to other mac
Make sure that project.properties is not corrupted.
I'm trying to deploy my app to a device and i get the following error
Error 27 An attempt was made to load a program with an incorrect format.
the odd thing is that the file and project this error relates to are both blank.
It was a WP7 app but i tried converting it to WP8 app in hope of fixing it but that didn't help. Anyone got any ideas how to figure out what's wrong?
the only thing i could find for this error talks about a specific assembly being compiled for the wrong platform. but this is not an option in the Windows Phone project settings
Check the files in your project. Files that are not part of the project should be marked as "Buid Action = none" and "Copy to Output Directory = Do not copy". Some examples are file files "text". Try this, worked for me.
Did you get any conversion warnings when you converted the project? I've worked around problems like this in the past by creating a new Windows Phone solution, re-creating the same projects in the new solution, creating any needed sub-folders into those projects, and then copying over the code and content files. This is usually quick if there aren't a lot of projects & folders.
Not sure if this is the case with you, or if you've already solved the issue (since it is an old thread), but this happens sometimes when you target the wrong CPU type. For example, your project targets x86 while you have a 64-bit machine.
Follow these steps to (hopefully) fix the issue:
Go to project properties
Go to Build tab
Select Any CPU from Platform dropdown
Save and recompile
I installed a retail version of Windows 8 Pro. I downloaded and installed Visual Studio Express 2012. I asked for and received a developers certificate. Then I tried to create a hello world app.
From there I get a "Unable to Activate Windows Store App" message box when I try to debug the app. Most commentary on the web says delete build directories. This didn't work for me
Does anyone have a solution for how to fix this and debug my app?
This happened to me once too, but the deleting build directories advice fixed it. Specifically, you just need to delete the bin\Debug and bld\Debug folders in your projects. Their contents will be regenerated by Visual Studio when you rebuild. I assume that this is only one project since it's a Hello World app; otherwise I would ask if you deleted build directories from all projects in your solution.
You can also try running "Clean Solution" from the BUILD menu in Visual Studio.
I'm sorry...it's horrible if this is happening on a clean install as you describe.
I ran into the same issue, and tried rebuilding, cleaning, deleting temp files, rebooting the computer, etc... and nothing helped.
Then finally I made a release build then went back to debug. And now it works.
I have no idea what happened, nor if that really helped, but it's worth a try.
For me a RESTART of pc solved this error message.
For me the problem was that I created the app on a TrueCrypt mounted virtual drive and when I moved the project files to a normal drive then everything worked just fine. Weird.
I was getting the exact same error. In my case the culprit was a NuGet package. It had added an app.config file to the project and it was confusing VS. I removed the app.config file and it solved my issue.
I got the solution at Iris Classon's site.
This can be solved by Uninstalling the app from the start screen then again building the app from Visual Studio.
I had a similar problem, and the cause was creating the project on a USB thumb drive. Creating a project on a normal hard drive volume works.
this can happen when the application signing key (.pfx file) is missing.
Try the following:
Open the Package.appxmanifest file in Visual Studio
Go to the register "Packaging"
Select [Choose Certificate…]
Select the test certificate using [Configure Certificate…] [From File…], or create a new one using [Configure Certificate…] [Test Certificate…]
When using a test certificate, ensure that it is in the .gitignore file. There should be an entry like !**\*_TemporaryKey.pfx to include the key in Git.
Note: The certificate for release build should only be available to the build server and not included in Git.
Rebuild the project
This has happened to me in the past and I have always found that deleting the build directories resolves it.
However this time this is not working for me.
I have tried
- Rebooting
- Deleting build directories
- Running Build | Clean Solution in VS
- Renewing Developer Account
The only thing that will work for me is changing my Package name under the Package.appxmanifest
However I am not overly happy with this as a solution. I will keep investigating.
The issue might be caused because NuGet will try to add an app.config with binding redirects to Windows Store apps if it thinks it is needed. However, Windows Store apps don’t need app.config, and will actually fail to start with a very confusing error message if it is present.
And the solution in this case would be to Remove the App.config
This error generally comes when you try to deploy in debug mode.
I would suggest, deploy the app first in release mode and then try in debug mode.
This worked for me.
Making a new certificate works for me. For this, go to Package.manifest->Packaging, and follow the Choose certificate.... Click on Configure certificate and select Create test certificate. Give it a name and press OK.
Increasing the revision number of the package worked for me
Tried so many of the above fixes. Nothing worked (deleting bin, obj dirs, editing the manifest, editing the registry, changing package name, etc, etc.) My Avast antivirus software was running and so I uninstalled it completely. That was it. App now runs fine.
This sort of problems are common with Windows 8 Visual Studio. Such errors encounters when your developer license of Visual Studio has expired so you may want to renew or get a new developer license here's how you get that. How to get a developer license in Windows 8
And similar problem may also encounter with E_Fail issues here's how to solve Unable to activate Windows Store app E_Fail Issue
For me, the fix was a combination of two of these answers -
Renew the developer license (How to get a developer license in Windows 8)
And deleting the build directories (though I deleted more then the screenshot depicted) Delete the Build directories
NuGet will try to add an app.config with binding redirects to Windows Store apps if it thinks it is needed. However, Windows Store apps don’t need app.config, and will actually fail to start with a very confusing error message if it is present.
Solution:
Remove the App.config
and build again
For those who get a similar error but who are searching for a solution while debugging an IOT background app on a local machine specifically - you can find it here.
Using the search term "unable to activate windows store app the activation request failed with error" brought me here.
Because of Two things i resolved this issue.
Basically, we just need to delete the bin\Debug and bld\Debug folders in our projects. Those contents will be regenerated by Visual Studio when you rebuild project.
Just Restart the Visual Studio. And Clean Build and Rebuild the solution and RUN it.
Hope this helps.,
Playing with this issue for 3 days, tried every suggestions, nothing works. Until now!!!
The solution was this for me:
renew developer licence
build and deploy solution in Release mode (after this step it still not worked, but VS installed some packages in rpi)
start VS remote debugger with default account (http://:8080/#Debug%20settings)
configure remote device with Universal authentication mode (VS2017 -> Project settings -> debug -> target device: remote machine, authentication mode: Universal (unencrypted protocol))
...and now I can sleep.
Hope it helps somebody.
This gift was courtesy of Microsoft's automatic updates for VS2015 which was one of the 2 culprits:
KB3022398
KB3165756
It also broke SourceTree and other apps that draw the GUI - making an outline of the app but not drawing the contents.
For me changing the Package Name in Package.appxmanifest fixed the problem
In my case, the C# UWP app had a native library which failed in the application startup code, and called exit(1). The symptoms were identical to those in the question, though. Visual Studio would throw a message:
Unable to activate Windows Store app '88888888-6666-5555-4444-111111111111_abcdefgh!App'. The Acme.exe process started, but the activation request failed with error 'Operation not supported. Unknown error: 0x80040905'.
In addition, there was a message in the UWP app Windows log under Microsoft\Windows\Apps\Microsoft-Windows-TWinUI/Operational: event ID 5961, message:
Activation for 88888888-6666-5555-4444-111111111111_abcdefgh!App failed. Error code: Unknown HResult Error code: 0x80040905. Activation phase: COM App activation
Internally, the C# part would try to construct a native class instance from the App constructor, the native class constructor would encounter an unrecoverable error and bail. From the UWP subsystem standpoint, and from the debugger standpoint, though, this looked as something distinct from the mere programmatic exit. I'll leave this answer here, 'cause I've spent some time chasing various UWP failure scenarios instead of running under a native debugger.
I've replaced the exit() call with throw ref new Exception(E_INVALIDARG). At least this way the error manifests in the managed debugger, and the message is descriptive.
I've been having this problem a lot with a UWP Windows 10 app on Visual Studio 2019...for me the reliable workaround is to bump the Build number in the Package.appxmanifest file (Packaging tab). It's a huge pain...really hope Microsoft will sort this out soon
Any existing error in the code can also cause this issue. Make sure your previous version of the code is working fine. Compare the difference and make sure all looks good.
I was getting this error and nothing else worked so I had to dissect my program. Turns out I referenced a StaticResource in my App.xaml that didn't exist.
Seems like a silly error but you'd also think Visual Studio would pick up on something like that and throw a different error so if nothing else works, double check your application resources.
As suggested by #Iman in a comment, in the UWP project settings, enable "Compile with .NET Native tool chain".
(After trying just about every answer in this question)
IntelliJ 8.1 (also tried 9) was working fine without Tortoise SVN, but after I installed Tortoise SVN 64bit on Windows 7, I'm getting out of memory every time I launch IntelliJ.
Increasing VM memory allocation doesn't work no matter how much I increase.
I googled and found few information about this particular issue, has anyone got the same problem?
Had the same problem. Seems it was caused by TortoiseSVN upgrading Subversion working copy format to 1.7 (it asked me to do so), while IDEA is probably only able to work properly with 1.6 (since it's the highest version number it offers me when I checkout a new project). I use IDEA 9.0.2 BTW.
I solved this by checking out the project (using IDEA) into a new folder and not letting TortoiseSVN to upgrade working copy version. If you have any uncommited changes in the old folder you'd probably have to either commit them first via TortoiseSVN and then perform SVN update on the new folder or to copy them into a new directory by hand.
Tortoise SVN installation should not affect IDEA in any way. I have the same configuration (Windows 7, 64-bit, Tortoise SVN) and IDEA works fine. IDEA doesn't use command line SVN, it has Java implementation of SVN protocol via SvnKit library.
The only thing that can somehow affect IDEA is the system wide Subversion configuration file (c:\Users\<user>\AppData\Roaming\Subversion\config). Check that there are no weird settings in it or try to configure IDEA to use a different Subversion configuration directory.
Also check if this problem is reproducible in IDEA 10.5.x.
Yes... It is causing by SVN... If u checkout the code into a folder and use that folder for intellij, it throws "out of memory" exception. Copy the folder that u checkedout into another folder and try to open the project through that folder.. and it works!!!!! Atleast It worked for me.... Good luck guys..