Paul Gielens:ThoughtsService

another Endpoint to my thoughts

News

Syndication

  		•

Ads


Favorites

Projects

Download Neo2005 Preview (Entity Object Framework)

A couple of weeks ago I gave a short preview of the upcoming .NET 2.0 support in Neo. Since then only a select few tried the early bits which resulted in lots of great feedback, thanks! Unfortunately the subversion system at CodeHaus is temporarily offline, which is holding me off from merging my code. This made me decide to make the bits available to a larger public. Download the Neo2005 Preview_net-2.0 distribution. Feedback would be very much appreciated!

For additional information see:

Neo DSL
Neo2005 Preview
Neo nullable types
Neo .NET 2.0 Support
Run Neo on Visual Studio.NET 2005 and .NET 2.0

Posted: May 24 2006, 01:48 PM by p.gielens | with 14 comment(s)
Filed under: ,

Comments

Steve said:

Ok, downloaded and built.

Now, how do you use this?  :)

Any documentation or do I need to go through all the source code?
# June 3, 2006 2:55 PM

p.gielens said:

Hi Steve,

Remember it's a tech preview and significant harder to get started with. I suggest you first scan the information available on the Neo website (http://neo.codehaus.org/). Then build both the Neo.2005.sln and Neo.Tools.2005.sln solutions.

Before you can use the code generator in VS.NET 2005 you'll need to register the stool by executing the setup.2005.bat which can be found in \Neo\trunk\src\Tools\VsTool\Resources\. In the case that you already have an older VsTool registered you need to unregister it before registering the new one using regasm (see the setup.bat file for the appropriate paths).

Then I'd suggest to run the pubs unit tests which can be found in the Neo.Tests.2005.sln solution under \Neo\trunk\src\Tests\
# June 3, 2006 5:48 PM

Paul Gielens:ThoughtsService said:

There are hardly any enterprise applications not manipulating structured information in any way. Most

# July 16, 2006 8:11 AM

Fenokp said:

Hello,

I can't setup new Neo2005 in my VS2005. I can build new solution, I get new *.dll, but if I run setup.2005.bat from VS2005 cmd line I get follow message:

RegAsm : warning RA0000 : Registering an unsigned assembly with /codebase can ca

use your assembly to interfere with other applications that may be installed on

the same computer. The /codebase switch is intended to be used only with signed

assemblies. Please give your assembly a strong name and re-register it.

WHat can I do for using Neo2005 in VS2005?

# July 28, 2006 4:28 AM

p.gielens said:

Most likely you already have the VsTool for Neo/VS.NET 2003 installed on your system. You need to unregister the "old" plug-in using the resasm.exe tool. Change the path to the "old" Neo assembly.

regasm /codebase ..\bin\Debug\Neo.VsTool.dll /unregister

Then build both the Neo2005.sln and Neo.Tools.2005.sln solutions, and run the setup.2005.bat again. Also make sure the assembly is signed with the \Neo\trunk\src\NeoNeo.snk... should be fine default.

Let me know how this works out.

# July 28, 2006 11:46 AM

fenokp said:

It dosn't help. I have do all steps, but the result it's same.

Can you create installation package for VS2005 please?

I will use Neo in my project.

# July 31, 2006 4:02 AM

danielh said:

Thanks for releasing this, it looks great. The only thing that I'm not sold on is the use of partial classes for the concrete EntityObjects. I don't see what advantage this has over the previous approach (inheriting from abstract base class).

With the partial classes approach I lose the ability to define custom logic for object creation (ie the constructor is defined in the generated part of the partial class and is not safe to edit) and it is far more awkward to override the object properties (eg to add validation logic to the property or some business rules).

I don't have a lot of experience with NEO. Is there something that I'm missing?

# October 29, 2006 7:02 PM

Jeff G said:

Just wondering if anyone knows if this project is still active. I'm currently using the 1.4.2 version of NEO and love it. I use it with .net 2.0, but without VS 2005 integration (I use the command-line generator instead - as well as Sql2Neo). Personally, I could continue using this version without any real problems, but was curious if anyone knows if the next version is still actively being worked on.

Thanks.

# October 31, 2006 11:03 PM

Chris said:

Paul,

Have you used this for a production application?  

I'm currently using NEO 1.4.0 in a heavy transaction scenario, but I'm wondering if this code base could provide me some benefits around the nullable types and generics.  

I've noticed in your other posts, that you are working with ADO.Net vNext, which I've been reading about recently.  I'm optimistic that the ADO.Net team is on the right track, and the need for a third party ORM is going to rapidly diminish when it's released.  Unfortunately, I have needs now, and I can't wait for .Net vNext, so I'm working with NEO for the near future.

So, back to the original question:  "Do you feel like this code is at least as stable as the 1.4.0 distribution?"

# December 3, 2006 12:36 PM

Paul Gielens said:

Hi Chris,

I haven't but since I have only changed the top-level API of Neo (mostly the code generation part) it is just as stable as the 1.4 version. I haven't changed the transaction implementation so no change/benefits there.

Please give it a try an let my know your findings. It is still my intention to check-in the 2.0 support, depending on the input I receive on this CTP.

For (almost) direct support use the email link on the top of this page.

# December 5, 2006 4:51 PM

Ulu said:

I'm also very interested in becoming this an "official" release. I've been quite happy about Neo, but I miss nullables a lot. Would be great to have it checked-in.

# December 9, 2006 6:00 AM

Jeff G said:

We've been using NEO on a large scale project, and I must say, it's been very easy to learn, and makes coding a lot more fun and intuitive. Maybe I haven't spent enough time on the Ado.net vNext stuff, but from the tutorials I've gone through, it doesn't appear nearly as nice as NEO. That contorted syntax they came up with to get design-time support is just completely unreadable. NEO makes code readable. simply put. I hope community interest / support for NEO grows because this is the project we've all been waiting for.

# December 20, 2006 10:37 PM

howard said:

Please keep the work on NEO...!!!!

We've been using NEO 1.4.2 for about a year on a very large project and it works just great...!!!

It's an excelent project and it deserves to have a 2.0 release.

# August 2, 2007 3:41 PM

Sarabjot Singh Nannar said:

Can any one please assure me that NEO 1.4.2 can be used successfully with .NET 2.0. As i have read that it is still under active development.

I have my application which is using the previous versions of NEO (1.2.3.20068). We are in urgent need of upgrading the application to .Net 2.0 as we are facing problems with the previous version. One of the problem is the one which is getting discussed at:

neo.svn.sourceforge.net/.../ChangeLog

marked as "2005-07-25 erik"

# January 28, 2008 3:42 AM
Leave a Comment

(required) 

(required) 

(optional)

(required)