Sunday, November 29, 2015 Register   Login

This site uses DNS Made Easy. Use it for reliable and professional DNS services.

RSS Feeds

Entries for November 2009

 1980 Views ::  1 Comments RSS comment feed

I just finished fixing some bugs, and put finishing touches on PainlessSVN 1.1.0. This has been long in coming, and I'm very happy with the results. I am now concentrating on the installation script and testing it in different versions of Windows. I'm hoping that this takes no longer than a week (hopefully, less than that). I will reset the trial, so that people who have previously downloaded, can trial again.

Here are few screenshots of the new UI in Windows 7 Ultimate x64:

posted @ Wednesday, November 25, 2009 6:44 PM by Hector Sosa, Jr

Actions: Tweet This  Share on Facebook  Share on LinkedIn  Emakl  Permalink

I've decided that I have to be better at releasing things. I have several completed enhancements for PainlessSVN, but I have held back, because I wanted a lot of other ones to be done. No more. I will release a new version, when I do a bug fix or a single feature is completed and tested.

Proposed Roadmap:

PainlessSVN 1.1

  • Automatic Subversion server discovery
  • Automatic PainlessSVN configuration, if server is found in above step
  • Configuration wizard
  • More information on objects selected in treeview, on the contents pane
  • Status of svnserve Windows service, if any is found

These enhancements are done and have been sitting in my repository for a couple months. Just need to get this packaged for release. This will be done very soon, as soon as I get all of my release tools configured.

PainlessSVN 1.2

  • PainlessSVN Solo (Standard) released
  • Start and Stop Windows service for svnserve
  • The ability to create a Windows service for svnserve, if none is found

This code is also already written, and sitting in my repository. I still need setup the release bits for PainlessSVN Solo.

PainlessSVN 1.3

  • Repository grouping by Realms
  • Path-based security

These are about 50% done. The other 50% is for actually editing the Realms' information and configuring the path-based security. I haven't decided if I want to tackle drag-n-drop in this release yet, as I want to just put out what I already have coded.

PainlessSVN 1.4

  • Import of dump files

This code is done, but needs an UI. That will take some time to get right.

PainlessSVN 1.4+

This is code that I haven't written yet, but here is some of the stuff that I want to tackle:

  • Manage common actions done by hook scripts with a UI
  • Plugin system for custom server actions. Basically custom dlls that are usually done with hook scripts, but done with plugins instead
  • Enabling and configuring SSH on the server for svn+ssh:// protocols
  • Enabling and configuring SASL security
  • Downloading and installation of a Subversion distribution, ie Tigris, CollabNet, and SlikSVN
  • Editing and syntax-hilighting for already existing hook scripts
  • Create a better backup experience for repositories.

This is a lot of work for a single person, but it should keep me busy.


posted @ Thursday, November 12, 2009 11:03 AM by Hector Sosa, Jr

Posted in: PainlessSVN

Actions: Tweet This  Share on Facebook  Share on LinkedIn  Emakl  Permalink
 3005 Views ::  1 Comments RSS comment feed

Justin (who didn't leave a last name) left a comment on how to debug MMC 3.0 snapins in Windows 7 x64 and Visual Studio 2008. I want to put this on its own blog post, so that I can find it easier. I'll just repost Justin's comment here:

I recently struck this problem with VS2008 on Windows 7 x64 as well.
I eventually found a solution :)

The solution is to directly use the 32 bit version of mmc at this path:
C:\Windows\SysWOW64\mmc.exe rather than the one in System32.
you still need the -32 flag as in your screenshot.

When you try and debug via "C:\Windows\System32\mmc.exe -32" what actually happens is the debugger attaches to the 64bit version which starts the 32bit version(in SysWOW64) and then closes itself hence why it stops debugging immediately.

You can start the snapin that you are debugging on the command line. This is extremely convinient. Here's a screenshot with Justin's findings:

This is on the project's properties page, on the "Debug" tab.

Now, if I could just figure out how to get the keyboard shortcuts back. They disappeared a couple days ago, and haven't been able to get them back. *boggle*

posted @ Tuesday, November 17, 2009 10:41 PM by Hector Sosa, Jr

Actions: Tweet This  Share on Facebook  Share on LinkedIn  Emakl  Permalink

I'm an IT guy at heart. I came up through the operations side of Information Services, mostly because my degree is in Managment Information Systems (MIS). As an operations guy, I'm always on the lookout for utilities that will make my life at my desk easier.

Well, I came across one utility that literally left me dumb-founded, total mind screeching to a halt stuff. NirSoft has created a viewer for BSOD mini-dumps. Holy Freaking Cow Cheez Whiz! I wish I would have know about this one years ago, when BSOD happened several times a day.

I actually had a BSOD on my day job's workstation yesterday. I'm going to be playing with this baby tomorrow!

posted @ Tuesday, November 17, 2009 8:45 PM by Hector Sosa, Jr

Posted in: Utilities

Actions: Tweet This  Share on Facebook  Share on LinkedIn  Emakl  Permalink

I really needed to have taskbars across both of my monitors, especially since these things are huge (28"). I checked Scott Hanselman's utility list and tried UltraMon and DisplayFusion. Both left me wanting. I was browsing through the SuperUser questions, when I found that somebody had asked about multiple taskbars on Windows 7.

The utility mentioned over there is Actual Multiple Monitors. This one has Aero Peek, and will let you have a start button on both taskbars. Shweet! It's not free, but it does what I wanted. I will be sending them money ASAP.

posted @ Tuesday, November 17, 2009 8:27 PM by Hector Sosa, Jr

Posted in: Utilities

Actions: Tweet This  Share on Facebook  Share on LinkedIn  Emakl  Permalink

The current codebase for Text File Splitter has reached the point where it is too hard to maintain. About 90% of the new feature requests are non-trivial to implement, and I decided to rewrite it instead. I use this new code base for both Text File Splitter and the new Text File Mechanic.

This means that there will not be any updates until I release 2.0. Version 1.5.1 will be the last release under the current codebase.

Text File Splitter 2.0

  • Separate executables for the UI and Console apps
  • UI will have a text box that will give you the command-line to use for the current UI selections.
  • Automatic detection of file encoding
  • Very simple action system (Actual scripting in Text File Mechanic)

Text File Mechanic will be a paid app, but it will only be $9.95. I'm hoping that this is low enough that it will become an impulse buy.


posted @ Thursday, November 12, 2009 11:18 AM by Hector Sosa, Jr

Actions: Tweet This  Share on Facebook  Share on LinkedIn  Emakl  Permalink

I installed a bunch of stuff last night. Stayed up until 2:00 AM getting them ready and mostly configured. So here's a list of what I was working with:

.NET Reactor
Windows SDK for Windows 7 and .NET Framework 3.5 SP1
Clarius Visual T4

.NET Reactor was the one that gave me the most hassle. Thankfully, the company now has an automated page to recreate your license. I still need to document how to get these installed without hassle.

Now come the hard part. I need to go through the build system for PainlessSVN and make sure that it is working. I will probably need to tweak all of the different project types. FinalBuilder, .NET Reactor, and Inno Setup all have their own project files.

This next few days will be interesting...

posted @ Tuesday, November 10, 2009 9:29 AM by Hector Sosa, Jr

Posted in: .NET Tools

Actions: Tweet This  Share on Facebook  Share on LinkedIn  Emakl  Permalink

I'm finally done with moving to the new house. So now I've turned my attention to setting up my development environment again. I got all the majority of my dev tools setup and running correctly. I created the directory structure for all the PainlessSVN stuff, but I couldn't remember what was the actual repository name. I spent about 20 minutes trying to guess the name. Arrrgh!

I remoted into the server where I have the Subversion software installed, and downloaded PainlessSVN. I installed it, configured it, and had it running in less than a minute.

Bingo! I saw the names of all my repositories, and I was able to recreate my working copy. Wow, that was easy!

So now, I'm ready to start working on PainlessSVN again. I have some very nice things in the pipeline. I think I'm going to scale back on the features, so that I can release something to the public. I think that I will put the new configuration wizard into the release build, and release that to the public.

I don't have a time frame, other than it will be ready when it is ready.

posted @ Friday, November 06, 2009 9:46 PM by Hector Sosa, Jr

Posted in: PainlessSVN

Actions: Tweet This  Share on Facebook  Share on LinkedIn  Emakl  Permalink
Terms Of Use | Privacy Statement | SystemWidgets
Copyright 2002-2014 by SystemWidgets
Google Analytics Alternative