- Must run off computer aˆ“ no set up necessary
- Very little requirement (.NET platform is alright)
- It must work with real documents and files aˆ“ no databases or some such needed. Fundamentally, let me operate it and possess it instantly gather anything on disk, enabling me to categorize the products without mobile they around
- Metadata need to be kept with real files/folders. Basically move a folder manually, Needs it to retain the classes they belonged to
- Painless looking by name, description, class
- Automatically update installments like, it should connect to Winamp webpages and down load the latest installment if necessary
- Automatically install tools
- Establish audiences for graphics, PDF, HTML, etc.
- Reorganize files and files
An application that fulfill the basic requirement might be exceedingly beneficial to myself, but i might fundamentally wish one that satisfies these extra criteria as well. Im honestly thinking of starting this application as an unbarred supply project, but I am at this time overrun with other issues. Still, I think i may beginning it in the near future.
The laws is actually all C#, compiled as aˆ?Any CPUaˆ?, as a result it requires no problems running unmodified with both 64 and 32 little Inventors
I’ve an addin for AutoDesk creator 2009, printed in C# and a build job to go along with it. So that you can subscribe the addin with Inventor, I had to develop to join up the assembly with aˆ?/codebaseaˆ? switch, thus I generated a custom installer action:
The subscription laws run by subscription solution modifies some registry tactics under HKEY_CLASSES_ROOT . This worked okay on or windows 7, but when operate on my personal Vista 64, the create completed effectively, but did not sign up the addin with creator. Why turned into evident as I recognized that my Inventor installations can be 64 little bit aˆ“ which means it appears Chicago best hookup apps for the important factors making use of the 64bit view of the registry, whilst installer activity runs making use of the 32bit see.
The only problem is how-to run the installer as 64 little. I also wished to enable the exact same MSI to be utilized on all systems, very compiling multiple variations was not an alternative. And looking the net, I managed to get the effect that it wouldn’t solve the situation anyway aˆ“ at least maybe not without another tools.
A better solution we created is simpler: rather than using RegistrationServices item, I’m able to manually perform the RegAsm.exe instrument to register the assembly. To my Vista 64, there are two forms of this appliance:
The directories may not be similar on more machines, naturally. Happily, .NET gives the RuntimeEnvironment.GetRuntimeDirectory() fixed way which comes back the folder with the common vocabulary runtime. To my maker, it returns C:\Windows\Microsoft.NET\Framework\v2.0.50727\ inside installer activity. We could use this, coupled with RuntimeEnvironment.GetSystemVersion() to create the paths to 32bit and 64bit models from the appliance:
Passing C++/CLI delegate to local laws
Recently I had to interface a C++/CLI set-up with an indigenous DLL printed in C. This will be typically simple, nevertheless C DLL could boost an interior show and provided a means to experience the program informed of your celebration. In order to be aware, the application form has got to sign up a callback features which is invoked of the DLL once the celebration is actually brought up. The registration function is actually announced like this:
Utilizing a typical features for your callback is effortless, but i desired to use a .NET delegate in order for i possibly could change the local show into a .NET celebration. This scenario furthermore actually is sustained by .NET. All you have to manage would be to prevent the delegate from are relocated or collected because of the rubbish collector.