open WebSharper.UI.Next.Client
open WebSharper.UI.Next.Html
open WebSharper.UI.Next
Don't know why after update the Nuget package WebSharper.UI.Next from 4.6 to 4.7, these namespaces are not available... But in the project file (.fsproj), the reference looks good...
WebSharper.UI.Next was moved to WebSharper.UI some time ago.
Related
I have been trying to debug this for a few days already. I am not able to find a solution.
I have installed JumioMobileSDK via cocoapods. However, when I run the project I am getting an error:
First check your dependencies and update CocoaPods, then close your current project and open the .xcworkspace created in your project folder.
If that doesn't work...
Show the Report navigator (8. tab in left navigator of Xcode) and check the report. It should give you some info what is going on like:
framework not found Pods_[PODFILE_OLD_ABSTRACT_TARGET_NAME].
If it keeps the framework with the old name that no longer exists (next to the new one), remove it.
You have an awesome day! Contact me if you need any further help!
This question already has answers here:
Xcode 4.2 how include one project into another one?
(6 answers)
Closed 7 years ago.
May I know how can I use the whole application project in my another project in Xcode.
By simply dragging the whole project in my new project its not working ,showing the file is not imported , if I want to use any class of the existing project in my new project.
Thanks in advance.
Here are some great step-by-step instructions on how to add static library dependencies in more recent versions of Xcode.
Use these links .
Xcode 4.2 how include one project into another one?
XCode 4.2 and Using a Static Library Causing Problems
You need to create workspace (File -> New -> Workspace. In workspace you can add as much projects as you want.
I've been playing around with the Starter Edition of Xamarin Studio to determine if it will meet my needs. I understand (so I thought) the limitations of this edition; 32K compiled IL limit, no native libraries, etc. Now, I understand native libraries to be C/C++ libraries, or even native Java libraries. This does not seem to be the case.
I have a solution in Xamarin Studio with 2 projects. One is an Android Class Library, the other is an Android Application. When I reference the class library from the application project and build, I get the following error.
Your app references native libraries. This functionality requires Indie Edition or higher.
I beg to differ! Every .cs file in the referenced Android class library project is simple .NET code. What am I missing? I can successfully run the Tasky Android_Starter solution without issue, and it is made up of 2 projects like mine.
I had to delete the Resources folder and manually edit the Android class library project file in order to get this working. I looked at the Tasky sample's project file as a reference.
After deleting the auto-included Resources folder from the project, edit the .csproj file in a text editor to remove the following XML elements:
Project\ProjectGroup\AndroidResgenFile
Project\ProjectGroup\AndroidResgenClass
With those things taken care of, I no longer get the error. I'm guessing, Xamarin Studio thought I was referencing another Android application instead of a class library. Not sure why the default project template includes things to break such a flow, but perhaps I'm not "doing" right" either. Go figure.
Deleting the Resources folder and manually editing the csproj file didn't work for me. I had to create a new C# Library project instead of creating an Android Library Project and import my .cs files into that. After that it compiled and ran fine.
I am working on a different iOS project in Unity and I have built it by exporting to Xcode (like I always have).
Whenever I try to open the "Unity-iPhone.xcodeproj" in Xcode, it gives me the following error:
Project cannot be opened because the project file cannot be parsed.
I have looked everywhere but cannot figure it out.
The project name does not have any spaces in it.
I have checked the .plist and everything looks fine.
The bundle identifier matches that in .plist.
This has worked in previous projects but now I am getting this error for some reason. What gives?
Today, I've been facing this problem (Unity Ver. 5.5 Windows Based system).
When I try to open my windows exported iOS project, i got "(..)the project file cannot be parsed". So, I decided to explore the project file, located in:
{Project path}/Unity-iPhone.xcodeproj/project.pbxproj
It is a plain text file, so you can use any text editor.
I found a line with a mismatched quotes. It was:
shellScript = "\"$PROJECT_DIR/MapFileParser.sh\""\nrm -rf \"$TARGET_BUILD_DIR/$PRODUCT_NAME.app/Data/Raw/QCAR\"";
To fix the problem, simply remove the quotation mark located at:
(...)MapFileParser.sh\" " \n(...)
It should be:
(...)MapFileparser.sh\" \n(...)
and it will be parsed correctly in xCode.
It's an automated typo error!
Good luck!
Well, after a couple days I have found the problem and it all has to do with the naming of the *.a files that the plugins import.
XCode does not allow for files to have spaces in their names (of course) but I had not caught that 3 of the *.a files from plugins had spaces in them.
After removing these plugins (I have different plugins that do the same thing anyways) xCode was able to parse the build and create a project for me!
Be careful of spaces!
Incompatable version of Xcode?
Are you using plugins? Most modify the project.
Try creating a new project and creating a build. If it works, it's a plugin, otherwise an Xcode version.
Faced the same issue today (Unity 2017.1.1).
Nothing related with the answers above. I just made a mistake in the Profile ID in the Player Settings of iOS : Edit > Project Settings > Player > iPhone, iPod Touch and iPad Settings > Other Settings > Identification.
I was getting this issue in Unity 2017.2 this week (building on Windows and then copying the build files over to the Mac for use in Xcode), and can confirm that the fix to the shell script line to remove the double quote as described by Anibal Itriago above worked in my case. Even an entirely blank iOS project with Vuforia disabled was failing to parse, but the line fix seems to resolve it.
My issue was related to dropbox.
I use a pc for development and a mac to build in xcode, so I store my project in dropbox. Sometimes dropbox can corrupt .pbxproj or even .plist files going from pc to mac, so when I attempt to open a project on my mac, xcode will throw the above parse error.
I had to zip the xcode project folder on the pc side, then on the mac side pull it out of the dropbox folder and unzip it. Then move it back to its original location. It's a pain but it worked.
when I was building my project done in ASP.NET and C#, it produced the following error:
The type or namespace name 'SQLite' does not exist in the namespace 'System.Data' (are you missing an assembly reference?"
So, when I tried to add it as a reference, I was not able to find "System.Data.SQLite" in my library.
How do I overcome this problem?
You get it (as a dll), then add a reference to it.
download here
for example install to C:\Program Files\SQLite.NET and browse to:
C:\Program Files\SQLite.NET\bin
I found that the best way to do this is to enter the following into the Package Manager Console:
Install-Package System.Data.SqLite
Try to search for System.Data.SQLite.DLL file (using windows explorer search) or if you have not yet installed it just download it from the net.
For more information try to read this.
For those folks that downloaded SQLite but can't get the DLL to show up in VS2010:
I've downloaded the latest SQLite build for my environment, but I still couldn't get the DLL to show up under References> Add Reference> .Net tab.
To fix this, I went into the Add Reference Window and selected the Browse Tab and just browsed to the DLL file in the install directory\bin folder. Now it shows up fine.
You need to download System.Data.SQLite, then you can add it to your project.