Latest Templates and CodeSmith 2.6

---------------- Compile started -----------------

(4180,3): error CS0246: The type or namespace name 'PropertySerializer' could not be found (are you missing a using directive or an assembly reference?)

Build complete -- 1 errors, 0 warnings

---------------------- Done ----------------------

Build failed

Anyone had a problem with latest templates and CodeSmith 2.6?

We're working on this.

I need a solution for this too!
did you ever get an answer?

 

Also, is this NOT a problem with the PAID for Codesmith?

Jim

No this is not a problem with anything higher than 2.6.  The problem is the way CodeSmith passes properties back and forth into templates.  It does so using serialization.  When we added the ability to name all the CRUD methods whatever you wanted as an Expandable type in 3.2.  The 2.6 impelementation was not that robust and would croak when converting with an ExpandableObjectConverter.  So then we tried writing our own serialization process with it, and for some reason the property grid was getting the correct converter but the copying of the properties was not.  This is a 2.6 problem, and 3 of us worked far too long on the issue. 
So yes, it's currently broken in a few places for 2.6,

You can continue to use the RC1 which should still work with 2.6.  If you're extremely desperate to use this version, i can list the things that have to be commented out in order to work.

>>>If you're extremely desperate to use this version, i can list the things that have to be commented out in order to work.

 

I'm extremely desperate enough if no one else is...

Thank you!

if you're really that desperate, why not buy the latest version - it's not that expensive and you get a lot of bang for your bucks when combined with NetTiers!

 

Have to agree with the previous comment... development of this architecture is already a heavy workload on those actively involved... rewriting the templates to support an out of date version of Codesmith rather than people paying $99 dollars for the standard version would divert attention from potential improvements that could save thousands on a project....

With support for different database providers, new versions of Enterprise Library due next year, Vista / WCF, LinQ etc, it does not really make sense to tie oneself to a legacy version of a code generator, with so many opportunities to advance the core product.

I appreciate all of the hard work BUT, could somebody change the web site and state that codesmith 2.6 will not work with .nettiers. For those out there like myself who are just now coming across this and want to see how it works; it does not send a good message when it bombs out of the gate.

I would say either make a link to the release that will work with 2.6 or state that it will not work with 2.6 so we dont end up spinning our wheels. I am sure with all of the hard work you guys are doing you would want people to stick around instead of leaving very early in the game.

Also .nettiers is promted as "free" and it is not anymore. It is open source but you cant use it unless you pay$ novel idea.

-just my 2 cents

It's not as if we have this huge master plan to sabatoge 2.6, don't be silly.    This was a technical issue that we ran into, spent way too much time on, and we discovered that this feature is not compatible with both features. 

coffman:

Also .nettiers is promted as "free" and it is not anymore. It is open source but you cant use it unless you pay$ novel idea.

.netTiers is open source and free, (even those are two seperate things).  There's no charge.  We'll update the site to remove 2.6 support so that it doesn't cause anymore confusion for anyone else.  We apologize that it confused you.

This will be the final .netTiers release that supports 2.6, and can be found here:
http://www.nettiers.com/files/netTiers2.0.0_cs26.zip

Although moving forward, yes, 2.6 will no longer be supported.  There's just too many awesome new features in CS 3.2+ to not move forward with that.  It would cut compile time in the templates by 300% by not compiling all the templates dynamically. That's huge!  Then we could actually let the community plug-in their own templates.  .net 2.0 support is a big one as well. There's really so much more, including having an updated schema explorer that we don't have to do our own workarounds to make up for the different versions of the schema explorer in all the cs versions.  This is a community driven platform, and the need for many of the new features far outweigh the cry for a completely 2.6 support.

Robert, on the subject of Codesmith versions, Ive received the email about the second beta of version 4.. any problems you forsee with the current templates / any assistance required with updating them to accomodate the new release...?

 

Again, can we get the documentation updated here. I have no issue that 2.6 isn't supported or that I have to buy CodeSmith now....actually, I feel like this has saved me so much time I owe it to CodeSmith (and the NetTiers team) to make a purchase. Unfortunately, it is frustrating that when I thought I could quickly upgrade to 2.0.0, I find there are Exceptions being thrown. After reading the included documentation and the website, I conclude my software is all up-to-date and I'm using the right versions. Then I google and receive this solution, only to find my software is in fact out-of-date.

As always, thanks for all the hard work.

 -Ian
 

Robert Hinojosa:

We'll update the site to remove 2.6 support so that it doesn't cause anymore confusion for anyone else.  We apologize that it confused you.

This will be the final .netTiers release that supports 2.6, and can be found here:
http://www.nettiers.com/files/netTiers2.0.0_cs26.zip

Hi,

The web site has not been updated yet, and I fall in the same issue.
Anyway I bought CodeSmith paid version because of the great value it had.
Just think of updating the "CodeSmith 2.6+" accordingly in the netTiers website "system requirements" section, so that people be aware of this.
Thanks for the amazing work on these tools.