search

TheSourceUK / tridion-2011-power-tools

Automatically exported from code.google.com/p/tridion-2011-power-tools
0 stars 0 forks source link

Create PowerTool Visual Studio template #21

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Instead of copying an existing tool and changing the code - with all of the 
steps needed to do that and to maintain the no-nonsense guide - I suggest we 
create a Visual Studio template for a new PowerTool.

That would simply involve create the various files with the given name and 
putting in some placeholder code/text. Then the developer can fill in the 
relevant code, rather than having to change irrelevant code first.

Original issue reported on code.google.com by pkjaer....@gmail.com on 11 Feb 2012 at 8:40

GoogleCodeExporter commented 8 years ago 
Started the attached and loaded it to Google Code downloads.

http://code.google.com/p/tridion-2011-power-tools/downloads/detail?name=Example.
zip#makechanges

Used $fileinputname$ to replace most instances of "Example" with user input.

Would $safeitemname$ be better?

I haven't checked this in--I'm not sure if this should just be a download, have 
it's own project, or be left in the Example folder (strictly speaking, the zip 
or set of files aren't a tool anymore). Also $fileinputname$ is a .cs file 
makes for a bad namespace name. I hacked it by adding ".txt" after the the aspx 
and code-behind names.

A separate template and/or code needed for the service side and configuration 
changes.

Original comment by reyes.al...@gmail.com on 24 Jun 2012 at 5:13