We’ve been kind of loose at Wintellect on how we deal with our open source projects. Many are published like mine on a blog or various open source hosting sites. After discussing it internally, we are now starting to push all our code to http://code.wintellect.com. That’s your go to place for our code. We’re hosting on GitHub because we felt it offered the easiest way for people to contribute to the projects. Our first three projects are up and ready for forking and using!
Do you want to make using Windows Installer XML a little easier? Paraffin makes creating and maintaining your file fragments much easier. Several people have emailed me cool additions to Paraffin that I’ll be working in very soon. The initial code post is Paraffin 3.6 which is the same published in this blog.
If you’ve read my blog for more than a few months, you know I’m all about better living through PowerShell. This module contains all the cmdlets from my blog and mainly revolve around making it easier to set up Visual Studio and WinDBG for symbol servers and source servers.
With Visual Studio 2012 dropping support for macros, what’s a developer who wants to do some simple automation of the IDE supposed to do? Download an SDK, write a VSIX, and have VS debugging VS possibly debugging something? Yeech. I converted all my macros to PowerShell so we can use the NuGet Package Manager Console for those simple extension.
On Aug 29 2012 5:09 PMBy jrobbins
Nice!
Hey John, one thing. I think the "Wintellect GitHub page" URL on the http://code.wintellect.com/ page is the private repository link and not the public one?
Currently the URL is, https://github.com/organizations/Wintellect
But shouldn't it be? https://github.com/Wintellect
Yeah, I know anyone who would come here or go there would be able to figure it out, but... (ahh... that's it, it's an initial test.. I get it! lol ;)
Greg,
Doh! Thanks, I messed that up. It wasn't supposed to be a test. :)
- John Robbins
Good.
John Thanks.
-bengalee
Hi John,
Paraffin is a useful tool, but when I need to prepare setup for localized project it still requires a lot of manual work. Usually we place culture dependent components into subfolders of main folder, then make the same structure in the wxs file, but I didn't find how to instruct Paraffin to keep file system structure in the generated code, is it possible?
For example, I could have
INSTALLATION FOLDER: foo.dll
de-DE: foo.resources.dll
fr-FR: foo.resources.dll
...
When Paraffin recursively works on INSTALLATION FOLDER, all goes to flat list.
Thanks,
Sergei
Sergei,
Paraffin keeps everything in the directories by default. If you run Paraffin on INSTALLATION FOLDER, you'll see that it keeps both foo.resources.dll's in their respective directories.
- John Robbins