Hi Firedancer
I wonder what your plans in terms of the .NET Framework 2.0 (Beta) are. I tried to open a project generated with your 0.9.0 RC3 SR-1 code in Visual Studio 2005 Beta 1, but the conversion (of your generated VS 2003 project into a VS 2005 project) failed.
Do you have any plans to make Paladin .NET Framework 2.0/VS 2005 compatible, or to even port it to .NET Framework 2.0?
My plans are to develop a smart client based on .NET Framework 2.0 in order to get click-once deployment as well as the new fancy GUI stuff.
I'm looking forward to migrate Paladin to .NET 2.0. The problem now is that I would want to learn up .NET 2.0 first and know what part to port over and what part to rewrite. The 0.9.x releases of Paladin and the BEWizard will not work on .NET 2.0.
I've started coding some basic classes for the next version. The version for .NET 2.0 will be called Paladin II (if I manage to work on it).
Thanks for the info.
Something that I think will be worth looking into is generics. It will allow you to have type-safe collections and lists, therefore removing the need to cast, etc.
I really hope you soon have the time to start work on Paladin II...
nidinidi wrote:Hi Firedancer I wonder what your plans in terms of the .NET Framework 2.0 (Beta) are. I tried to open a project generated with your 0.9.0 RC3 SR-1 code in Visual Studio 2005 Beta 1, but the conversion (of your generated VS 2003 project into a VS 2005 project) failed.