I've been experimenting with a simple Visual Studio project that packages a Xslt extension file into a Umbraco package, ready to be installed into a Umbraco 4.03 site.
There's no rocket science involved, this is just a basic Visual Studio 2008 project with some umbraco binaries, a sample Xslt extension class and a sample Web user control. Plus a file and a folder needed for package creation.
The target is people who does not already have a VS project for their Umbraco site and/or people that want to add some Xslt-funcionality quickly. - 1) Open the VS project, 2) add code in the existing class and 3) build 4) install the automatically created MyPackage.zip.
In this version the name space and package name is hard coded, but I don't see that as a problem for people beginning to add their own dlls and are using this to create one-site-packages. Future versions will perhaps have some naming features.
Would be cool to hear some opinions about this idea. And if someone has a minute, try the beta. http://bit.ly/979WOV
Naming, yep, I will do something about that. And a function that adds necessary xml in the package xml to add multiple extension classes / usercontrols is actually already on the go.
Simple sample Visual Studio Package creator
Hi!
I've been experimenting with a simple Visual Studio project that packages a Xslt extension file into a Umbraco package, ready to be installed into a Umbraco 4.03 site.
There's no rocket science involved, this is just a basic Visual Studio 2008 project with some umbraco binaries, a sample Xslt extension class and a sample Web user control. Plus a file and a folder needed for package creation.
The target is people who does not already have a VS project for their Umbraco site and/or people that want to add some Xslt-funcionality quickly. - 1) Open the VS project, 2) add code in the existing class and 3) build 4) install the automatically created MyPackage.zip.
In this version the name space and package name is hard coded, but I don't see that as a problem for people beginning to add their own dlls and are using this to create one-site-packages. Future versions will perhaps have some naming features.
Would be cool to hear some opinions about this idea. And if someone has a minute, try the beta. http://bit.ly/979WOV
Regards
Jonas
Just gave this a quick go end to end and it worked flawlessly.
I was trying to see where the 'Magic' happened and then I spotted its done in post-build event!
Naming features and being able to easily add multiple extension classes / usercontrols would be a plus although this isn't hard to do manually.
Nice simple project.
Max
Thanks alot for giving it a try Max.
Naming, yep, I will do something about that. And a function that adds necessary xml in the package xml to add multiple extension classes / usercontrols is actually already on the go.
Regards
Jonas
is working on a reply...