I'm working on a project with a friend, we are using git for version control. They created the unity project and I pulled it to my computer as well. Every time I open the project, I have 2 blank compiler errors. I cannot click on them to open VS because they seemingly do not exist.
I can confirm as well we are using the same unity version (2019.2.15f1) both on Windows machines (mine is Win10)
Here is a list of things I have tried as suggested by other forums and my teammate:
Deleting and recreating library folder (results varied from no effect to unity no longer launching)
Creating a new directory and launching a fresh version (worked correctly on their system, not mine)
Reinstalling Unity
Triple checking that my version is up to date
Reinstalling Unity and Visual Studio
Changing the scripting framework (suggestion was to downgrade from 4 to 3.5, we were already on 2 for some reason)
Edit: Here's a picture of the errors
Edit 2: Attempted to open new project in older version of unity, the following error appeared
Edit 3: Upgraded to Unity v 2020.1.0a14
Edit 4: Never mind, now it's not even letting me open the project anymore. Complete with a cool fun new error.
Edit 5: It just... started working. I reinstalled unity again and it just decided to work.
It seems that your project use some packages that aren't installed in your project.
Try to re import the packages mentioned in this image:
enter image description here
I'm working on a windows Phone OLD application. I'm getting this issue related to SQL3.dll. in visual 2015.
Unable to load DLL 'sqlite3': The specified module could not be found. (Exception from HRESULT: 0x8007007E)
What I've tried, Done Cleaning all project, added sqlite.dll in Bin/debug folder, but I could not overcome this issue.
here is a screenshot.
I've tried adding a dll as reference (sqlite-winrt-3220000.vsix) but this is not compatible.
Any help would be appreciated.
Add the dll as a reference:
Right-click in "References" in the project you want to use it in and select "Add reference".
Select the option "Browse" and use the browse button to select the dll you want to include.
Add a using statement to the class.
After this you can use the dll in the project.
I've tried adding a dll as reference (sqlite-winrt-3220000.vsix) but this is not compatible.
SQlite is distributed as a VS extension. To add reference to your project, right click on References, “Add References”, “Windows Phone 8”, “Extensions”, check “SQLite for Windows Phone”, press OK.
No other steps are required, you don’t need other references and you don’t need to specify or deploy DLLs manually.
Also sqlite has different extension for WP8.1, you should probably install another one, sqlite-wp81-winrt-3220000.vsix.
Update: I think you’re trying to build for a platform that’s unsupported by SQLite library. SQlite for windows phone only supports 2 platforms, intel 32 bit (for emulators) and ARM (for devices and for the marketplace). It does not support AMD64, and it does not support “Any CPU”. You’re probably trying to build “Any CPU”, it’s usually the default platform for .NET.
Another possible reason is wrong project type. Your project has to be windows phone 8.1 app, not universal, i.e. the project name in the solution explorer panel must end with ”(Windows Phone 8.1)”
Update 2: I’ve compiled a simple app that uses sqlite, run it in emulator and it worked flawlessly on my PC. Ensure your references look like this:
If you have the same, make sure you have VS 2015 Update 3 installed. If you already have it, repairing your visual studio installation might help.
I have a Xamarin Cross Platform App in VS2017. I'm trying to add WCF service references and it seems I need to be able to uncheck Windows 8 and Windows Phone 8.1 from the list of Targets. However, I'm unable to do so.
When I right click on the project and choose properties I see this:
Project Properties showing Windows 8 and Windows Phone 8.1 as targets
When I click the "Change..." button I only see these options:
Change Targets options that don't include Windows 8, or Windows Phone 8.1
The "Install Additional Targets" link just takes me here: (Not helpful)
https://www.microsoft.com/net/download/visual-studio-sdks
Any idea how I can remove these targets and start making use of my WCF web services?
Thanks in advance!
Thanks for your comment Hans.
For anyone else running into the same problem with adding a Service Reference I followed these steps, which don't make any sense, but they worked:
Right click on the Xamarin project and choose Manage NuGet Packages. Uninstall Xamarin Forms.
Close and re-open Visual Studio.
Right click on the Xamarin project and choose Properties. Click the "Change..." button under Targeting. The .NET Framework dropdown was automatically set to 4.5 for me. I changed it to 4.6. Click OK. (Mine still said 4.5 on the properties window, but that's OK)
Close and re-open VS.
Go back to Manage NuGet Packages and reinstall Xamarin Forms.
Close and re-open VS.
Viola. Magic. I can now add Service References.
Currently I am trying to add service reference for mine Portable Class Library (PLC) in my Xamarin.Forms apps. For that point, I read that I have to remove Windows Phone 8.1 target platform.
I am opening PLC properties and I see where the target platforms are, there I find WinPhone and Silverlight, unfortunately when I click Change they disappear and I cannot remove them.
Screenshot of libraries
Can anybody suggest what the issue could be and how can I fix it?
Please keep in mind that I am doing it with Visual Studio Community 2017 (version 15.2).
Thanks in advance
1 option is to change the .net profile version manually in your .csproj file.
Visual Studio unload your current PCL Project.
Edit your .csproj File (Right Click on the unloaded project)
Find Node <TargetFrameworkProfile></TargetFrameworkProfile>
Change Value to Profile7
Save and close the file.
And than reload your .csproj file.
Another way is to uncheck Asp.Net Core when clicking on Change button. That will give you the Add ServiceReference instantly.
First of all I would like to say that I already tried all the solutions I could find on the internet, including Unable to Activate Windows Store App
I recently upgraded my Windows 7 machine to Windows 8.1 to be capable of developing Windows Store apps using Visual Studio 2013. When I open a blank project (Windows Store -> Blank App) and run it I get this error:
Unable to activate Windows Store app 'Package Name'. The App1.exe
process started, but the activation request failed with error 'The app
didn't start'.
See help for advice on troubleshooting the issue.
I already tried:
Reinstalling Windows (Clean install)
Reinstalling Visual Studio 2013
Installing Visual Studio 2012 (same error)
Deleting "bin" and "obj" folder
Cleaning the solution
Uninstalling the app from start menu
Creating a new project
Acquiring the license multiple times (the license is valid)
Making sure that app.config doesn't exist
Investigating the Windows Event Log which says
Activation of the app 'Package Name' for the Windows.Launch contract failed with error: The app didn't start..
but found nothing useful
Adding a new Windows user
Run everything as administrator
and at last, changing the desktop background :)
None of this did bring a solution. Does anyone have an idea what else could be the reason for this error?
Thank you.
I found a solution. The problem was that the drive I was working on was encrypted (TrueCrypt). Moving the output folder to an unencrypted drive solved the problem.
If switching from x86 to x64, make sure your Project Properties Platform Target and Configuration Platform are BOTH set to X64.Hint you need to change to x64 debugging in the Build menu/Configuration Manager dialog to get the Configuration Platform in Project Properties to update.
This caused the activation error problem to be resolved for me
HTH
Robert
I had the same Error and tried after loading the SQLite Package for WP 8.1 some things above:
not working:
Clean and Rebuild
Restart Computer/Phone
what did the deal (for me)
I put Platform Target under Properties -> Build to ARM instead of x86
Hopefully this might help somebody else facing this ridiculously informative Errormessage.
I had the same problem with Visual Studio Community 2015 while trying to debug an Blank App (Universal Windows) using Visual C#.
Visual Studio was installed on Disk C:(SSD), and Project files were placed on D:(HDD). I´ve created a Folder on C: Drive and placed my test project there.
After that Error messages gone.
If you are receiving this error and are developing for Microsoft Hololens:
You are trying to build to a device that is asleep. To wake your device, tap on the button on the back (on/off button).
Good luck!
I've tried all the solutions found on the net and none applied to my case, not even this one.
The only way I could make it work was changing the Package Name in the appxmanifest.
This made me think there must be some leftovers somewhere around with the old package name, that are either corrupted or inaccessible because of some permissions issues.
It might be just a coincidence but the problem appeared twice after I tried using the app verifier (appverif.exe)
Now I reassociated my app to a store app package and things seem to continue working...
In my solution, I have a non-UWP project (Multiplatform development) that builds with a different Solution Platform.
I was attempting to run the UWP project in Debug, but as the wrong Solution Platform.
Edit:
I also get this when I build my project for Any-CPU, instead of x64.
Ensure that ALL APPLICATION PACKAGES has "read" permissions on C:\Windows.
My organization's group policy likes to strip all permissions from C:\Windows, including the ALL APPLICATION PACKAGES group . By adding it back in and setting Read & execute, List folder contents, and Read, I'm able to run the app from Visual Studio without any problems.
See What to do if your Windows 8 Modern App fails to start for more tips, including this one.
I had the same problem in Visual Studio 2015 Update 3, Windows 10 Build 10586.494.
The error came up when trying to start any UWP app that I compiled without .NET Native Toolchain. With Native Toolchain enabled, the apps would start.
Installing a new (blank) app manually fixed the error for me:
Start VS 2015
File > New > Project.
Blank App (Universal Windows) Visual C#. OK.
Make sure to be in Debug config
Right click on Project > Store > Create App Packages
No. Next.
Select Debug for all architectures.
Create
When packaging is finished, open Explorer to the project path / AppPackages / [...]_Debug_Test
Right-click on Add-AppDevPackage.ps1 > Run with PowerShell
Follow the instructions
Start the installed app from Start Menu
I had the same problem a couple of weeks ago. A simple restart helped me out.
Also tried this one?: http://irisclasson.com/2012/11/04/problem-unable-to-activate-windows-store-app-the-app1-exe-process-started-but-the-activation-request-failed-with-error-the-app-didnt-start/
Hope its usefull to you
I managed to fix the same problem by rebuilding the solution. (In Vis Studio 2012)
I have tried many solutions and nothing worked. At the end what worked for me was to change the startup project to windows phone 8.1 and after it runs OK I changed it back to windows 8.1 and it runs OK. It works for me as I am making a universal app. Hope it helps anyone else.
I had the same issue with a Windows Store App after moving some files around. I ended up opening an older file (as Admin) to see if it would run and found that it did. I then returned to the file that would not and it ran also. I believe opening the older file (as Admin) reset the paths for development and the permissions. Hope this helps.
Same problem - moved my project from the TrueCrypt Partition and all was fine.
I had a similar issue, solved by choosing a new publisher certificate. And of course restarting Windows
I had same issue. Selecting proper Platform solved my problem. i.e. My application was selected to run under x86 platform, while my OS & SDK supports x64. Selecting x64 solved my problem.
I had the same problem on a UWP app when creating a package for Testing, but not when runing directly from Visual Studio 2017.
The solution was to select only the architecture that I am using to Debug the App, Instead of all options (x86, x64, ARM).
Here is the option choosed on Visual Studio
There are can be a couple of things that might be causing this problem.
Here are the trouble shooting steps that helped me out:
Step 1 : Check to see if running visual studio in the elevated mode (Run as an Administrator) helped solve the problem. (Sometimes, your folder permissions might get mangled due to various softwares that you might have install)
Step 2 : Delete all the bin and obj folders in your project and rebuild the projects in your solution manually.
Step 3 : Do a quick check of your System Type (x64 or x86 etc) and see if your project is targeted for the same.
Here is how to do know your system type: Win + R > cmd > systeminfo
If it says x64, then make sure to select the Solution Platforms (In visual studios top action bar) as x64 or so forth depending on your architecture.
Thats all I did to solve my problem.
I had unticked an option while trying to get debugging working prior to this error, the fix for me was to re-check the "Compile with .NET Native tool chain"
A rather niche situation and solution...
I was remote debugging a UWP app for a while successfully. After some reworking, I ran into this issue. In the main app project I had set the windows version compatibility accordingly (I am running the app on a Windows 10 IoT Enterprise 2019 device) but had forgotten to match those windows target and minimum versions for the Library Project that was in my solution.
After cleaning and re-deploying the solution (first uninstalling the app from the remote device), the problem went away.