Spring.Web

[battleace]

How will the specifications change for ASP.NET 2.0?
Will there be any major changes when you make changes that are specific to .NET 2.0?
I intend to write an app using .NET 2.0
Should I wait for a release of Spring.web that is .NET2.0 specific?

[battleace]

The Spring.Web library extends ASP.NET by adding a variety of features such as Dependency Injection for ASP.NET pages, Bidirectional data binding, Master pages for ASP.NET 1.1 and improved localization support.



This makes me think that you are coding specifically for 1.1

Is anyone going to reply????????????????????????

[Aleks Seovic]

Hi,

Yes, our current preview release of Spring.Web has only been tested with ASP.NET 1.1 and was written primarily to fix shortcomings in ASP.NET 1.1.

That said, we will make it ASP.NET 2.0 compliant and make sure that all of the features mentioned still work. Some things are likely to change a bit. For example, data bindings might be defined a bit diferently because of the partial classes, master pages will leverage ASP.NET 2.0 master pages functionality, while still allowing you to configure them using DI, etc.

The goal is to have support for both ASP.NET 1.1 and 2.0 applications by the time we ship official Spring.NET 1.1 release (EOY), and there should be another preview release (or possibly RC) around .NET 2.0 release date.

That said, you can start using DI features of Spring.NET now, as those are not likely to change. By simply changing .aspx handler to Spring.Web.Support.PageHandlerFactory you will be able to inject dependencies into your ASP.NET pages, regardless of whether or not you use features from the base Spring.Web.UI.Page class.

BTW, how urgent is your need? If you need something right now I will make sure that at least basic stuff works fine in ASP.NET 2.0. You will have to get the code from CVS though, so let me know if that's an option for you.

Regards,

Aleks

[battleace]

Thanks for the reply.
My database design is complete.
I am skilled in ASP.NET 1.1 and learning 2.0 now.
So I have some time.
EOY is fine but I need to know what approach to take
so that I will be compatible with Spring.NET 1.1 when it is released.
Is there anything that I need to be aware of while
working on the architecture?
My goal is to be as loosely coupled as possible.
Ibatis.Net is part of my architecture plans.

[Rick Evans]

Hi

I'll second everything that Aleks has said... I'm currently writing the integration classes for iBatis.NET at the moment, so if your architecture is going to be using iBatis.NET for data access, you'll be well catered for by Spring.NET.

The SpringAir reference application that will be released as part of the Spring.NET 1.1 release will demonstrate all of the supported features for Spring.NET's web support, inclusing an iBatis.NET backed implementation of the DAO interfaces.

Ciao
Rick

[Aleks Seovic]

Well, Dependency Injection will definitely help you to decouple your classes, so that would be the first thing I would plug into if I were you, especially because it isn't going to change even in 2.0.

I would also create a custom base Page class for the application that all other pages inherit from. That way you can easily plug in other Spring.Web features later by changing your base class to inherit from Spring.Web.UI.Page instead of System.Web.UI.Page.

I think if you do these two things you'll be well on your way to adopt Spring.Web within your ASP.NET 2.0 app when we ship 1.1 release.

Later,

Aleks