To build WDS from the repo …

… you’ll have to have a 7.x SDK registered for any Visual Studio version before 2010. Currently I build with Visual Studio 2005, but solutions exist also for 2008 and 2010.

The reason for this new limitation is that I implemented the progress inside the Windows 7 taskbar buttons.

Side-note: preliminary elevation support exists and I will try to finish that up over the weekend. Thanks to Chris. Once that stands, the next step is to work on limiting the memory use.

More to follow soon,

// Oliver ;)

PS: I used the 2D-icon set for now. It looks quite good also and since it’s not a release version it doesn’t matter too much. Oh, and the icon is partially responsible for why there were issues with VS 2005, too. If you have problems with the icon set in VS 2005, try copying the rc.exe and rcdll.dll from the SDK bin folder into C:\Program Files\Microsoft Visual Studio 8\VC\bin (or wherever you installed your VS 2005).

This entry was posted in Alpha, Pre-release, Project news. Bookmark the permalink.

9 Responses to To build WDS from the repo …

  1. James says:

    How is it going with the development ?
    You haven’t updated the online repo in 6 weeks :???:

    Any plans on releasing a new version soon with the special ntfs filesystem code in it ?

  2. Oliver says:

    Indeed. I’ve been busy migrating my servers and will be so for at least two more weeks.

    If you have followed the blog comments you will know that the NTFS code is not stable to be included in WDS. Yes, there are plans to release a (beta?) version within the next two, three months and hope for much feedback.

    As you pointed out, the code in the repo is up to date. Feel free to send patches against that. The bug tracker is kept up to date, too – and there is a lot to do. But only I am currently writing code at all.

    Edit: if you’re curious. This blog is now running on the new server as well. And the migration of the UltraVNC forum is still before me …

  3. James says:

    Could you please upload the NTFS code, i’m very interested in reading it. Also i have worked with the NTFS filesystem before so i do have some experience with it so i might be able to help.

  4. James says:

    So do you not want help ?
    You could always send the src by e-mail if you don’t want to upload it to the online repo

  5. Oliver says:

    Hi James, apologies for the delay. Was preoccupied because someone accused me of hosting malware on one of my servers (sent an abuse notification to the hoster of my server). This took up the better part of this week. You can imagine that this is pretty bad for someone like me working for an AV company. This case seems to be closed now.

    No, I have not uploaded that code because a.) it is not stable and b.) I have not made up my mind as to whether I will put it under GPL or a more lenient license compatible with the GPL. There are so many other places in WDS that could use some love, so help is always welcome.

    Patches are easier with Mercurial, but I’m ready to grant commit access quickly. There is no reason not to.

  6. James says:

    Well the src repo is for developers only so it shouldnt matter if its stable or not (you just have to mention it somewhere)

    At the moment my interest is in the ntfs filesystem which is why i offered my help with that code. I’m not currently interested in other parts of this project. I might be in the future but right now i’m not.

    As i’ve said before i can work on the code privately and send you patches when needed until you have made a decision on the license stuff.

  7. Oliver says:

    Hi James, absolutely. The repo is for developers.

    However, just because I’m project admin and contributing developer doesn’t mean that I have to publish prototype source that is not even part of the WDS project. I will do that under the conditions (license) and at my discretion at the time I choose. Not right now, though.

    Sad to hear you’d not be interested in contributing to other areas of WDS that would certainly require more care than a planned experimental feature, but that is your decision as the one to introduce my code (and when and how) is mine ;)

    If you ever had the problem that someone from a company takes your code “in private” and then the company tries to go after you when you publish your stuff on which they based yours, you could perhaps relate. It’s a different story though.

  8. James says:

    You tease :|

    My interests change often and right now it’s fat32 and ntfs filesystem.
    When it comes to open source projects i get into it by being interested in a specific part of the project and then move on to other parts because as i work with this part do improve other parts as well while i work and i also get ideas of how to improve the overall projects, etc..

    I think your paranoia is getting the better of you but i understand, I’ve read about bad people stealing open source code before. Though i have not read anything matching your scenario.
    Too bad i can’t convince you to share the code yet.

    Do you have a time table of when you will release the src ?

  9. I had some really weird issues while setting up Visual studio 2010 with Qt 4.7. The most important thing (that I stupidly didn’t realize) was the fact that you CANNOT use the VS2008 compiled libraries and dll’s (available on the Qt webpage) if you don’t have VS2008 installed. The reason is because the Qt SDK you download is a debug build which is dependant on the VC9.0 DebugCRT, meaning it needs the Visual C 2008 Debug Runtime installed, which is NOT available as a redistributable installer. The only way to install the DebugCRT is to install the entirety of Visual Studio 2008.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>