Jasper and C#

re: Jasper and C#

Andres Aguiar — Fri, 04 May 2007 23:52:30 GMT

Why don't you build a BuildProvider for ASP.NET that generates the classes dynamically? That way you don't need late binding and you can use it from C# in ASP.NET.

re: Jasper and C#

aconrad — Sat, 05 May 2007 05:34:41 GMT

For a few reasons we don't use ASP.net build providers:

1) We also want to support Avalon and winform apps with the same Jasper API and experience.

2) ASP.Net build providers statically generate code - not dynamically at runtime like Jasper. So in reality, this would not be a huge improvement over the EDMGen utility currently being shipped as part of the Entity Framework.

3) We are trying to make Jasper a data access API geared toward iterative & agile development. This means supporting scenarios like changing the database without recompiling the app and working in interactive environments like the Python REPL utility – either of which will work with build providers as they exist today.

re: Jasper and C#

Panagiotis Kanavos — Mon, 07 May 2007 10:48:13 GMT

Aren't C# type inference, extension methods and the like enough to implement Jasper's functionality? Why should a project that uses Jasper have to use a late binding language?

There are over 30 ORMs and frameworks in the market that don't have this limitation which use every conceivable method from Dynamic Methods (NHibernate) to Reflection to code generation, that don't have any language dependencies.

Furthermore, the agile community is predominantly C# oriented. By providing a VB only data access API you may annoy the very crowd you are trying to please.

re: Jasper and C#

Andres Aguiar — Tue, 08 May 2007 14:51:49 GMT

Hi Andrew,

OK about 1 and 2

On 3, it's true, but from the development experience point of view is equivalent (or actually better as you have intellisense) as the compilation is performed at runtime.

Regards

re: Jasper and C#

Steve — Wed, 23 May 2007 17:29:55 GMT

// can now call

var stories = myDynamicContext.GetQuery("Stories");

Story myStory = stories(0); //get first story

myStory.Title = "New Story Title";

This code will not work... stories(0) was probably ment as stories[0] but the stories instance has no type information... So I guess what it ment to be was:

// can now call

var stories = myDynamicContext.GetQuery<Story>("Stories");

Story myStory = stories[0]; //get first story

myStory.Title = "New Story Title";

re: Jasper and C#

aconrad — Mon, 04 Jun 2007 22:07:46 GMT

thanks - fixed the array indexer call. It is hard constantly switching between languages.

However, note when you call GetQuery, you don't need to specify the type T. We have a non-generic version.

re: Jasper and C#

Jason Kergosien — Tue, 09 Dec 2008 23:44:57 GMT

I heard a while back that Project Jasper was discontinued, but the code may be used somewhere in ADO.NET.

Where can we get some information on this?

Thanks,

Jason Kergosien

re: Jasper and C#

aconrad — Fri, 12 Dec 2008 20:30:54 GMT

Not that I know of. We have been waiting for the DLR to mature before proceeding with dynamic languages.