Liteservandroid is an application that is used as Http api/Restful api to connect to CouchDB from TouchDB. I got a sample project and when i tried to build the project, i got the following error.
Gradle: A problem occurred configuring project ':LiteServAndroid'.
Failed to notify project evaluation listener.
Configuration with name 'default' not found.
There were no pointing errors in the code section. Can any one help me to find a solution.
Thanks
Chinna
The first hint I see with your problem is that in August 2013 you are talking about TouchDB - and TouchDB name change was introduced as far back as January 2013. There are old projects sitting out there using out of date code.
Are you sure you are using the newer code base? Here is the direct link to the ListServAndroid project https://github.com/couchbaselabs/LiteServAndroid
I found Couchbase Lite to be a bit tricky to integrate. They have moved it all over to Android Studio for building and developing too... so that might be new learning also. Have you gotten the GrocerySync test application working?
Related
When I check out the latest source from one of the sample projects of Catel (Logviewer/CsvTextEditor) and I build my solution.
I get a lot of build errors.
All of these error are related to one error:
The name 'InitializeComponent' does not exist in the current context.
I've both tried to build the solution in Visual Studio 2017 (15.9.11) as well as Jetbrains Rider.
Can anyone help me with this issue?
Some of the libraries require .net core 3.0 (see https://github.com/dotnet/core-sdk) and might require VS 2019 prerelease.
I'm a new hololensdeveloper and I recently made a Hololensproject using net scripting backend just because there were way more information on how to set it up and get it working with Visual Studio.
Now when I feel somewhat confident I decided to change it up to il2cpp, but I have a major issue.
Everytime I put a c#script(even empty ones) into any folder within the application the Hololens won't even start it. The screen goes black for some seconds and then returns me to the mainpage.
This feels strange as all the scripts from the HolotoolKit works fine and they are written with c#.
Im currently using
.Unity 2018.3.4f1
.HolotoolKit 2017
.Visual Studio 2017
Thank you!
-----Solved------
SO after alot of time, I switched to Unity LTS and that fixed my problem. Feels bad that I have to rely on an older version.
If I remember correctly, using the HoloToolKit and not the mrtk v1 or v2, you should use Unity LTS 2017. Maybe thats the problem?
And I'm not sure if I understood you the right way. So you are building it in unity and than deploying it to the HoloLens without getting any errors in your console?
Also changing the scripting backend framework, means using a different build directory and If you are not doing that Unity should give you a message like "Build path contains project built with IL2CPP or .Net"
I am attempting to convert the Microsoft.Health C# class library that is installed as part of the HealthVault SDK, using instructions provided here. After following these instructions, I get the following error when attempting to load the project into Visual Studio 2013.
"The project is targeting frameworks hat are either not installed or
are included as part of future updates to Visual Studio. See
http://go.microsoft.com/fwlink/?LinkId=287985"
Visiting the link takes me to .NET SDKs and Downloads. Once there, I have no clue on what needs to be done.
I do realize that one will have to leverage the Portable Class Library Contrib project to fill in some missing bits, especially code related to System.Security. This, I will deal with later.
Any one run into a similar problem?
Maybe so late but for those who have the same problem.
I had the same error in a project which was working perfect before updating VS2013 and finally after 3 hours looking for the source of the error I found that the error is about TargetFrameworkProfile.
In my case I sloved it like so:
Right click in the unloaded project in your solution and click Edit.
Find the TargetFrameworkProfile tag and set it as below:
<TargetFrameworkProfile>Profile78</TargetFrameworkProfile>
At a guess, this is because you need to specify the TargetFrameworkVersion and TargetFrameworkProfile properties in the project file. Compare the .csproj you are trying to create to a newly created PCL project file, and make sure that everything that's not specific to your project matches.
I ran into the same issue and got it resolved by installing the latest Visual Studio Update
I tried without success to get a SharePoint 2013 application page or web part to work with Entity Framework 6 (6.0.1 to be exact - the version installed into Visual Studio 2012 by default using NuGet at time of writing).
My code was very simple for test purposes, just reading data from one table.
I could install the package just fine, create models, see that the they were properly configured etc, no problem - but whenever I tried to load the page I got the error:
Event code: 3008
Exception type: ConfigurationErrorsException
Exception message: An error occurred creating the configuration section handler for entityFramework: Could not load file or assembly 'EntityFramework' or one of its dependencies. The system cannot find the file specified. (C:\inetpub\wwwroot\wss\VirtualDirectories\[sitename]\web.config line 36)
I copied all of the config settings from the App.Config file in VS (created by the EF install), into the web.config, verbatim.
I tried every suggested fix I could find on the interweb (e.g. changing the EF assembly ref to "Specific version = false", changing version refs in the config file to the specific version... all sorts) but nothing worked.
I created a console app using the same settings and it worked fine, so I know it's not a server-specific issue - looks like a compatibility issue with SP2013, anyone have any ideas?
I installed EF 5 using the NuGet console, and finally got it working with that... but I'm very curious as to why EF 6 refused to play ball.
Thanks
Poolio
You need to deploy the Entity Framework assemblies (EntityFramework.dll, EntityFramework.SqlServer.dll) as part of your SharePoint solution package. You can reference external dlls in the package.
I have recently taken control of maintaining our continuous integration system which provides installers (mostly for projects built using Visual Studio and the .NET Framework).
This uses CruiseControl.NET server side and CCTray client side so developers can 'fire' new builds of software when work has been completed. Source control is provided by Sourcegear Vault.
One of the build projects has started failing in the last few days with the following error as soon as you force a build via CCTray:
System.Exception: There is no version 0 of $/xxx/yyy in [repositoryName]. at ThoughtWorks.CruiseControl.Core.Sourcecontrol.FortressClient.GetVersion(String repositoryFolderPath, String workingDir, Int64 folderVersion) at ThoughtWorks.CruiseControl.Core.Sourcecontrol.FortressVaultSourceControl.GetSource(IIntegrationResult result) at ThoughtWorks.CruiseControl.Core.Sourcecontrol.MultiSourceControl.GetSource(IIntegrationResult result) at ThoughtWorks.CruiseControl.Core.IntegrationRunner.Build(IIntegrationResult result)
I have checked ccnet.config and the build script for this project but everything seems correct.
Does anyone have any clues? There have been no upgrades to anything on the development server as far as I am aware.
We've just had the same problem. I don't know how we ran into it exactly, but we had killed ccnetservice before.
However I found out that the file ProjectName.fortressState was missing. I recreated that file from another project, renamed it to "ProjectName.fortressState", modified the content and restartet ccnetservice.
After that the project worked again on ccnet.
I have experienced the same problem here for a few projects. None of the previously suggested solutions have resolved it and Vault support is non-responsive in their forum:(
The only workaround Ive found so far is to create a project that builds this (whatever) with a new project name.