Comments for Fiberglass flowers

Comment on Self-update library for .NET using WiX: DotUpdater by Fernando

Fernando — Tue, 16 Mar 2010 22:11:22 +0000

Victor, thanks a lot. It looks like this would be very useful. I have being 4 or 6 hours checking your source code. I had to convert it to vb.net, but after that it has begun to work.

But I don’t know how to make rss files. I don’t understand very well your “readme.txt” guide. I don’t use NANT so I will write my own rss files with notepad++ or similar.

Could you help me ? What is exactly the struture of rss files ? Is it easy to do with notepad++ ?

Thanks a lot.

NOTE: When I finish my work, I will write you back with all of my experiencie in it. May be you want to publish my “little experiencie”.

THANKS

Comment on “Project Dependencies” of Visual Studio 2008 broken in MSBuild by Alexey

Alexey — Mon, 15 Feb 2010 15:31:36 +0000

I mean, chuvak, eto genialno, spasibo!

Comment on “Project Dependencies” of Visual Studio 2008 broken in MSBuild by Alexey

Alexey — Mon, 15 Feb 2010 15:30:49 +0000

?????, ??? ?????????, ???????!

Comment on Algorithmic quiz: check a 3-braces expression by Victor Sergienko

Victor Sergienko — Fri, 12 Feb 2010 15:40:29 +0000

IIRC, we both solved it back in 1993

Comment on Algorithmic quiz: check a 3-braces expression by Leon Dubinsky

Leon Dubinsky — Fri, 12 Feb 2010 15:22:04 +0000

You’ve just solved an MS interview question I used to ask a while back…

Comment on Self-update library for .NET using WiX: DotUpdater by KraKot

KraKot — Wed, 13 Jan 2010 12:59:42 +0000

Hello! I’ve read u previous article about update! I have msi instuller made with WiX and need updater. I tried ClickOnce but as far as u understand, application should be published with ClickOnce, not msi to use update clickonce. In your dotupdater there is only dll file, could u tell the main stratagy u use to create this library,if its possible.Thanks a lot!

Comment on Can’t run .NET bootstrapper from an MSI by Boyan Kostadinov

Boyan Kostadinov — Sat, 07 Nov 2009 09:11:48 +0000

Finally got around to checking out what you are talking about with WinRar. I did get the issue you were talking about but not all the time. Anyway, WinZip Self-Extractor works but requires a separate license. As an alternative DotNetZip lib has a self extracting component and a command line tool: http://dotnetzip.codeplex.com

Comment on Grails: mocking domain objects in unit tests by Victor Sergienko

Victor Sergienko — Wed, 04 Nov 2009 08:16:09 +0000

Great, thanks.

I wonder — will save() work and what will it do.
And will addTo*() assign both ends of connection.

Anyway, will migrate when 1.2 is released and will know it all.

Comment on Grails: mocking domain objects in unit tests by Søren Berg Glasius

Søren Berg Glasius — Wed, 04 Nov 2009 07:47:38 +0000

When using Grails 1.2-M3 this is nolonger needed (as far as I can see)

/Søren

Comment on Self-update library for .NET using WiX: DotUpdater by Ryan

Ryan — Tue, 15 Sep 2009 03:20:05 +0000

Thank you so much for the quickstart guide and the fast response! This will be very helpful!

Comment on Self-update library for .NET using WiX: DotUpdater by Victor Sergienko

Victor Sergienko — Mon, 14 Sep 2009 12:41:36 +0000

You’re right, I need to elaborate on some kickstart instructions.

Will do when I have the time.

Definitely, not every RSS, only one of a specific structure, containing version, file path, etc.
You need a RSS feed and a MSI, not EXE file – a full new version installer package.

You don’t need to use WaitExec or PostExit binaries, it’s an internal stuff. They don’t have instructions included, but the code is pretty clear.

UPDATE: Quickly hacked a quickstart guide out of old code. Feel free to ask questions.

Comment on Self-update library for .NET using WiX: DotUpdater by Ryan

Ryan — Sun, 13 Sep 2009 05:36:37 +0000

Also – I am curious, is there any basic example or instructions on how to use the WaitExec and PostExit. Is it that you pass the PID of the running app that needs updating to WaitExec and then pass the PID of the WaitExec to the PostExit? Then the filename of the setup.exe to the PostExit?

I think I’m missing something… umm…

Comment on Self-update library for .NET using WiX: DotUpdater by Ryan

Ryan — Sun, 13 Sep 2009 04:52:41 +0000

It looks like this would be very useful. I really want to try it out but I am not sure exactly where to start. Just a quick question and I apologize if this is a really simple question.

I am curious – will this work with any rss? I am curious how you generated the rss file?

It looks like I need an rss feed and a setup.exe. Then for checking if an update is available I need to “CheckForUpdates” using the updater?

Comment on Self-update library for .NET using WiX: DotUpdater by Fiberglass flowers / Auto-update with WiX

Fiberglass flowers / Auto-update with WiX — Thu, 03 Sep 2009 11:53:09 +0000

[...] Update: for a ready solution (library), see official release announcement [...]

Comment on Auto-update with WiX by Victor Sergienko

Victor Sergienko — Thu, 27 Aug 2009 11:50:22 +0000

fayssal,
I never managed to get ClickThrough autoupdate – it was too immature. I just took a FeedBuilder class out of its source and crossed it over with Updater Application Block.

I’ll check if I can publish the component source. That should be useful for many.

edit: Probably I’ll be able to publish a ready component on CodePlex. Will update in some days.

edit2: You got it: http://victorsergienko.com/self-update-library-for-net-using-wix-dotupdater/

Comment on Auto-update with WiX by fayssal

fayssal — Wed, 26 Aug 2009 10:00:06 +0000

Hi Vector,

Did you manage to have any running instance sample for using ClickThrough for auto-updates? It would be great if you could some sample code if you have it.

Thanks.

Comment on On unit tests in Visual Studio 2008 vs NUnit by Victor Sergienko

Victor Sergienko — Tue, 17 Feb 2009 15:23:28 +0000

That “supported” is a word people fall under magic of.
Effectively this means that “some issues have a chance to be resolved in the next release in one or two years”.
We had quite a big issues with TFS, and that is what happened.

For NUnit, you have ways greater chance of someone resolving your issue in time, if not yourself.
So, I’d say: (-4) NUnit is opensource and has a good community support.

For second item, it’s also arguable. To turn VS into a good IDE, I demand ReSharper.
Which supports NUnit ways better then VS does for VS.Test.
Which brings us back to “(-2) GUI that shows where test failed is ugly”

Comment on On unit tests in Visual Studio 2008 vs NUnit by Anonymous

Anonymous — Tue, 17 Feb 2009 15:12:32 +0000

(+5) it’s supported by microsoft
(+5) they can be run by anyone with VS2008, no external dependencies

Comment on “Project Dependencies” of Visual Studio 2008 broken in MSBuild by Victor Sergienko

Victor Sergienko — Fri, 09 Jan 2009 14:47:24 +0000

Doug,
This might be tricky. Check if you’re using right GUIDs in right order (in the line with “} = {“), and that you caught all necessary dependencies.
My MSBuild is of the same version.

Comment on “Project Dependencies” of Visual Studio 2008 broken in MSBuild by Doug

Doug — Fri, 09 Jan 2009 14:34:46 +0000

Unfortunately, this does not seem to work with my MSBuild.
vs2008, sp1