Installing Raven via Visual studio

[Idan]

I try to install RavenDB via visual studio and get

PM> Install-Package RavenDB -Version 1.0.888

Attempting to resolve dependency 'NLog (= 2.0.0.2000)'.

Attempting to resolve dependency 'Newtonsoft.Json (= 4.0.8)'.

Successfully installed 'NLog 2.0.0.2000'.

Successfully installed 'Newtonsoft.Json 4.0.8'.

You are downloading RavenDB from Hibernating Rhinos, the license agreement to which is available at http://www.ravendb.net/licensing. Check the package for additional dependencies, which may come with their own license agreement(s). Your use of the package and dependencies constitutes your acceptance of their license agreements. If you do not accept the license agreement(s), then delete the relevant components from your device.

Successfully installed 'RavenDB 1.0.888'.

Install failed. Rolling back...

Install-Package : Already referencing a newer version of 'Newtonsoft.Json'.

At line:1 char:16

+ Install-Package <<<<  RavenDB -Version 1.0.888

    + CategoryInfo          : NotSpecified: (:) [Install-Package], InvalidOperationException

    + FullyQualifiedErrorId : NuGetCmdletUnhandledException,NuGet.PowerShell.Commands.InstallPackageCommand

 

PM> 

I really don't know how to get started working with the DB, hheelllppp!!

[Fitzchak Yitzchaki]

You have two options here:

1. Remove the reference to Newtonsoft.Json dll, or any package that may use it. Re-install RavenDB.Client package.

2. You can use an pre-release package, using the -Pre parameter, which doesn't conflict with Newtonsoft.Json dll that you may have.

[Idan]

not working

PM> Install-Package RavenDB -Pre

Attempting to resolve dependency 'NLog (= 2.0.0.2000)'.

Attempting to resolve dependency 'Newtonsoft.Json (= 4.0.8)'.

Successfully installed 'NLog 2.0.0.2000'.

Successfully installed 'Newtonsoft.Json 4.0.8'.

You are downloading RavenDB from Hibernating Rhinos, the license agreement to which is available at http://www.ravendb.net/licensing. Check the package for additional dependencies, which may come with their own license agreement(s). Your use of the package and dependencies constitutes your acceptance of their license agreements. If you do not accept the license agreement(s), then delete the relevant components from your device.

Successfully installed 'RavenDB 1.0.910-Unstable'.

Install failed. Rolling back...

Install-Package : Already referencing a newer version of 'Newtonsoft.Json'.

At line:1 char:16

+ Install-Package <<<<  RavenDB -Pre

[Fitzchak Yitzchaki]

Use RavenDB.Client packge:

Install-Package RavenDB.Client -Pre 

[Idan]

I installed the client package, but how can I install the server, how to manage it, how to add data without doing it via code, any UI?

[Itamar Syn-Hershko]

Idan, please go through some docs, everything you need is documented there

http://ravendb.net/docs/intro/quickstart/adding-ravendb-to-your-application 

http://ravendb.net/docs/intro/basic-concepts 

http://ravendb.net/docs/studio 

http://ravendb.net/docs/client-api/connecting-to-a-ravendb-datastore 

[Damian Hickey]

Have you read this? http://ravendb.net/docs/intro/quickstart/adding-ravendb-to-your-application

[Radenko Zec]

Hi guys.
I am still receiving same issue with latest stable version of RavenDb Client when installing with newer version of NewtonJSON.
Can you please merge your dependent DLL-s into Raven.Client.LightWeight dll so we can work normally ?

http://blogs.clariusconsulting.net/kzu/how-to-merge-your-referenced-assemblies-into-the-output-assembly-for-improved-usability/
http://www.red-gate.com/products/dotnet-development/smartassembly/features/#merging-dll


Thanks

[Chris Marisic]

RavenDB.Client 1.0.972 uses  Newtonsoft.Json (= 4.5.7)
RavenDB.Client 1.0.960 uses  Newtonsoft.Json (= 4.0.8)

RavenDB.Client -pre internalizes Newtonsoft.Json

RavenDB.Database 1.0.960  uses  Newtonsoft.Json (= 4.0.8) period and there is no other option. Only the client can use 4.5.7 without breaking.

RavenDB.Database -pre internalizes Newtonsoft.Json

[Radenko Zec]

Hi There.
Some of us planning to use RavenDb 1.0.960 in production.
We don't want to install unstable build 1.2 to solve this issue.
Can you please fix it in this version of RavenDb ? You have a no idea what problem this issue is cause to us....

[Chris Marisic]

https://groups.google.com/d/msg/ravendb/-2FKa2D0Eds/fDinCfcLWT8J

Not Oren's fault.

[Radenko Zec]

Not agree with you Chris.
You can simple merge your external dependencies(dll-s) like JSON.NET into single client dll (RavenDb.Client) using tools like
SmartAssembly or ILMerge.
Instead you are forcing us to use Unstable builds of RavenDb...

[Chris Marisic]

You are grossly oversimplifying things. Yes you can ILMerge, however Raven actually uses the publicly exposed type information of JSON.NET to facilitate how raven works. There are times when you reach right into json.net through raven.

So no, Oren cannot just ilmerge json.net and have everything work. He needs to build an entire typing/configuration layer on top this to act as a mediator between external code usage and internalized json.net usage. This is a non trivial task, this was one of the many things they've done in 1.2

All of these issues would have been avoided to start with IF james netwonking didn't continuously release breaking changes and instead built software that was (binary exectuable) backwards compatible.

[Oren Eini (Ayende Rahien)]

At any rate, the issue is pretty much settled. We aren't going to have another 1.0 release ,and we are going to go full steam ahead at 1.2 to make sure it is out ASAP.

[Radenko Zec]

That is your point of view as consumer of JSON.NET.
From my point of view (I am consumer of your client library) you are responsible to internalize all external DLLs in your client DLL.
I don't want to go into discussion is this trivial task or not (I have done it many times and I know exactly how much hard is to create mediator for external dll...)
I just want to point out (as you have also pointed to James Netwon King bad backward compatibility) that you have delivered v1 client with a serious issue and you don't plan to fix it until next release which is also unprofessional.
I am also looking forward to see release 1.2 ASAP.
Thanks

[Oren Eini (Ayende Rahien)]

Radenko,

Actually, we delivered 1.0 without an issue. The WebAPI issue came later, and I am sad to say that my crystal ball failed to specify that exact scenario, which is probably while I hurled it out of a tall building. I believe that its last words were "I did not see that coming".

We have a stop gag measure, in build 971, which allows you to use the 4.5 version of json.net on the client.

I am aware of the issues for testing, but the solution for that is 1.2 for now. 

[Chris Marisic]

I certainly agree with you Oren. There's no way you can be held accountable for a project that badly manages releases that haven't occurred yet.

@Radenko Oren specifically used JSON.NET in a public fashion to give users the greatest harmony for already existing JSON.NET code, especially if you have elaborate serialization schemes. He didn't want users to have to duplicate things that work for JSON.NET to work for RavenDB.JSON.NET. This was the right choice. Unfortunately he and the entire community have been significantly let down by James Newtonking's failure at project and release management.