Delphi Open tools Api creating a project wizard - delphi

I am trying to create a project wizard and am totaly new to the open tools api.
I got the following questions.
Is it possible to save the project to a specific loaction and if so how can I do that. My wizard asks for the location.
I create a new form but it has the name Form1. I like to give it a specific name. How can I do that?
I like to copy a datamodule to my project. How can I tell the wizard to copy the file and save it in the project directory with a different name?

As a start look at this question Create a Simple Delphi IDE Expert
look also here
http://www.mustangpeak.net/ (view the wizard section) and here:
http://www.tempest-sw.com/opentools/
best regards,
Radu

Related

VS2013 AddIn into VS2015 VSPackage: How can I create ToolWindow2

Can anyone please guide me how can I convert Add-Ins to VSPackage Extention without recreating/replicating everything into VSIX?
I have one addin which is supporting VS2010 to VS2013. I have everything in .sln. I want to migrate/create .addin into .vsix for compatibility issue of VS2015. After few research, I have found that the code what is written in IDTCommandTarget.Exec method has to run into my custom command class of vsix project...
So, I created a new .vsix project in same solution & add a reference of my .addin project into .vsix project and I am able to load initial controls of my addin project as like below...
enter image description here
but as per the code, I want to create CreateToolWindow2 on double click of my tree node but I am getting following error (null AddInInstance)...
enter image description here
Can anyone please guide me how can I create an Instance of AddIn class to create ToolWindow2?
This is not quite the way to do this. You create a .VSIX project, then add a Custom Command, and you add the code/logic that was in your old addin's Exec method, to the custom commands MenuItemCallback method.
Note, you no longer need to programmatically create the menus/commands, toolbars, etc. VSPackages have an entirely different (and much more effective way) via the .VSCT file.
FAQ: Converting Add-ins to VSPackage Extensions
To convert an add-in to a package is not easy or trivial, you need to use .vsct file to create menus, toolbars, commands, etc.
About toolwindows:
The usual way for packages is:
HOWTO: Create a toolwindow with a ToolWindowPane class in a Visual Studio package
http://www.visualstudioextensibility.com/articles/packages/
But you can do it in the same way as add-ins:
HOWTO: Create a toolwindow without a ToolWindowPane class in a Visual Studio package
(same link)
About not "duplicating everything" when migrating an add-in to a package, see my post:
Strategies migrating from Visual Studio add-ins to packages

How to pack whole ROS project

I have made my ROS project down, and have tested the program successfully, then i need pack my project and give it to my customer.
I am confused about how to hide my source code and pack my whole ROS project into one application maybe, can anyone help me?
The easiest way to do this is to create a shared object (that will hide all your source code).
This can be done in the CMakeList with add_library.
Once you have your mystuff.so, you can give it to your costumer (along with an example main.cpp and some documentation).
Your costumer will put a target_link_library in his CMakeList and will be able to use your stuff.

Developing Umbraco with Visual Studio - best practices

I have two environments that use Umbraco: Live and Dev.
As I have in research, Umbraco will be create a physical file when a user creates a new partial view, macro, etc. so, I have two questions:
1. What is the best way to know which files were created on Live and how to migrate them to Dev environment for the purpose of creating new features?
I have tried to Google and found "Hybrid Framework" but it is not up to date and I want to maintain code by myself.
2. I want to extend Umbraco with my own code. What is the best practice for this? (I do not want to change any code in the original Umbraco Source, just create my own new code)
As I know, I can create a package for extending code but I just want to know the other ways.
Partial Views, Macros , Templates are .cshtml files, these will not affect your source code. Same is case with css and js files; these will not harm any source code.
Just copy paste these files in respective folders and reload the nodes in backend. It will work properly.
Other way is you can create a package zip file from developer section where you can export datatypes, content and files, and install it in other environment.

Seeking framework or skeleton for stanard desktop applications

Every application seems to start with me taking a similar app, thowing out the "meat" of it and using the skeleton for my new project.
I don't always get all that I want from a previous project, nor do I need everything from it, but certain things keep cropping up again and again:
about box (with contact email being generated from the app name & version number direct from the project options)
splash screen (source & duration)
only allow single copy to run
prevent task switching
acccept dropped files?
minimaize to tray
hide from task manager
recent files list
that sort of thing.
I used too have such a skeleton for C++ Builder, years ago. It just read an .INI file and customized the app's behaviour accordingly.
Before I take the trouble to port it to Delphi, does anyone know of anything similar which is freely available?
You can simply create your skeleton project and add it to the repository (IDE menu Project\Add to Repository).
If you want to be able to dynamically create different projects based on some parameters (user input) you can also write a wizard using the OpenTools API.

Changing the generated code for "Add View"

I would like for the generate "List" view contents to have a check added to it to first check that the model has elements, it occurs to me that I have no idea how these views are generated. Can those be changed?
Visual Studio uses "T4" (Text Template Transformation Toolkit) templates to generate the code when you ask for a new file, and yes, they can be edited.
Basically, you find the default templates, copy them into your project, and then edit them to create project-specific custom new-item templates which VS will use instead of the defaults.
A good set of basic instructions can be found at:
http://blogs.msdn.com/webdevtools/archive/2009/01/29/t4-templates-a-quick-start-guide-for-asp-net-mvc-developers.aspx
They are T4 templates located in:
Program Files\Microsoft Visual Studio 10.0\Common7\IDE\ItemTemplates\CSharp\Web\MVC 2\CodeTemplates\AddView
Also take a look at this article, it describes how to change the templates on a per project basis.
There is also another option, where in the MVC project you can make a folder called CodeTemplate and put the .tt files in there. Then those templates will be used as well.

Resources