I've been trying to use Ink for my Unity Project.
https://assetstore.unity.com/packages/tools/integration/ink-unity-integration-60055
After installation through the Package Manager, everything on Unity seems to work fine (Ink files can be created, they get compiled to JSON, the Ink Player tab works, etc etc) - with one exception:
I can't get VisualStudio to find the Ink namespace. I've tried restarting it and Unity. It worked fine for other packages like the new Unity Input system and TextMeshPro.
What can I do to fix this?
Edit: Regenerating project files with all checkboxes checked doesn't seem to work either.
Edit 2: If I open a C# script from Ink itself (Asset/Ink/), then VS seems to recognize Ink.Runtime. Its only in my own scripts (which are also in Asset/) that don't have the namespace:
In this case, I managed to fix it by deleting the ".vs" folder inside the project folder.
Related
I have multiple Unity projects on this PC, however this problem only affects one of them, the one which is connected to Plastic SCM named "My Daughter's Adventure". Please ignore the name :). If I try to open a c# script from Unity, it opens it like this. However, the correct .sln file does indeed exist in the correct folder, shown here.
If I try to open one of my "offline" projects, everything works fine. Image here.
Now, I can open the .sln file manually and then open the script file from Unity. That brings back Intelisense and that little code dropdown menu, but this method has been kind of bipolar. Sometimes everything works fine, otherwise I get errors in Unity regarding the name of the script that doesn't correspond with anything and it asks me fix "compile errors" even if there aren't any.
Do note that I tried everything, at least what I could find online in terms of fixing this, including the preference settings in Unity. I'm also kinda new to Unity and Visual Studio. It took me 3 hours just to identify the problem and made an account just for this problem. Can anyone help me?
I have a problem on a Xamarin.Forms solution on Visual Studio 2019 (and 2017):
I seem to have lost any Intellisense on the solution. If I try to navigate to an object, i get the message "cannot navigate to the symbol under the caret", even for something declared in the same project. I don't have any colors, nr autocompletion.
I've tried to clean, delete obj and bin folder, rebuild, remove .vs folder, reset user data, reinstall VS.... no change...
BUT, If I remove the package Xamarin.Forms, it fixes it ! The problem is that if I reinstall it and restart VS, it comes back...
For information, the solution build and works without any problem.
That solution didn't have any problem previously, it appeared lately, and I can't figure out what caused it.
The version of Forms used is 2.5.1.444934, but I tried to update without succes.
I don't know what to do anymore...
Edit : I'm adding 2 captures on the same code, one with Forms added as a nuget package, and one without.
The various objects are all declared in the same project, same namespace as AffaireSync.
Without Forms, they are recognised (and DependencyService isn't, but that's normal as it's in Forms).
And With Forms, everything is white, nothing is recognise, nothing is colored, nothing is underlined red...
Without Android Forms
With Android Forms
Ok, I deleted tried a few revert on my solution sources and it didn't fix my problem.
So I deleted my local solutions, checked it out again, and it's all fixed... I can't figured out what happen, but it works, so I'm not touching anything...
I'm working with XNA 4 in VS2010. Recently a crash corrupted a .contentproj file of mine. So I deleted the content project inside VS, created a new one and repopulated it with the contents of the old one. However the new content project did not properly hook up to the rest of the program, whenever I build the program its contents aren't translated to .xnb-s and placed inside the content folder of the game as when I built the program with the original content project.
I'm sure I'm missing a step in reconnecting the new content project, I just can't seem to be able to find out what that step is. Any ideas?
Thank you.
Take a look at the properties of the imported files in Visual Studio and check they are correct. Check the Build Action specifically. It should be set to Compile.
I found a way to make it work. More a workaround than a solution, I created a new VS solution, imported everything other than the content project from the old one and used the content project that came with the new solution.
Win 8.1
JAVA-ADT ver 22.3 first installed last week with updates
Android SDK Manager used to get needed files for JellyBean
I followed the instructions for creating MyFirstApp.
It worked just fine until I "Close all" then "delete" project from Package Explorer.
When Importing or New-project-Android project from existing code-root directory-Copy project into workspace using MyFirstApp the "Androidmanifest.xml" and ".project" files contents are completely erased. It loads with major manifest errors once then never again with no way getting the MyFirstApp reloaded.
I have only one Workspace folder for projects and tried creating several versions like MySecondApp, MyThirdApp and so on. All get manifest.xml contents erased.
I'm unable to get a project reloaded into JAVA-ADT without it erasing contents in androidmanifest.xml and .project. This is my first try at JAVA-ADT.
I tried "project" "Clean" before closing out the original MyFirstApp with no success either.
I have read and read posts but can't figure it out. Lots of hours on developer.android.com training too.
What am I doing wrong?
I have to create around 200 WP7 apps that are very similar. They differ only in the content, icons and name. So manually create them isn't a good idea so let's I've written a little tool, which does the following:
Copy the created template project
Copy the content files from a source directory to the copied template.
Change the app name, tile name and app id in the WMAppManifest.xml
Add the copied content files in the .csproj-file.
This works and the generated project opens error-free in Visual Studio 2010 and compiles without errors. The xap-file can be deployed on device and emulator.
The problems:
If I want to debug the app by pressing F5 in Visual Studio I get "The application could not be launched for debugging. Ensure that the target device screen is unlocked and that application is installed", both for device (which is unlocked and connected with Zune/WPConnect) and the emulator.
If I try to start the app on the emulator it closes immediatle after start. BUT if I start the app on my device it works like a charm. Crazy stuff.
The curious stuff: If I do the things which my little tool does manuelly I can debug the project from Visual Studio.
This only occures with my generated projects. Every other WP7 project (existing or newly created within VS) works and debugs error-free.
I tried to PCs: Win7 x64 with VS2010 Ultimate and an other one Win7 x64/VS2010 Pro and on both maschines I have the problem.
Maybe someone has an idea which causes the problem. Thanks for the help!
Edit: I've seen something new: The AssemblyInfo.cs file is located in the properties folder and correctly included in the csproj-file. But if I try to open the Assembly Information from the project properties all fields are empty and if I try to set them I get an error ("value is not in the expected range" or something like this).
I've got similar problem with some sample programs.
It turned out that I have to set in a Solution properties:
Active config => Debug|Windows Phone
it works for me
If they only differ in content, icons, and name, would it be simpler to make one complete app, copy it 199 times, and then just put the appropriate files into the correct directories?(if you made a tool to make templated projects, i'm sure you could do this with code too)
Plus that way if you ever need to change the program you can just recopy with that code again, but not copy the content, thus updating all of your individual 200 apps.