Rick Brewster

Ok this one should go a lot smoother. I went through a lot of the technical details on my blog: http://blog.getpaint...nd-net-v4-woes/ This build does not require .NET v4, which should smooth things out For the full details, check out the blog post linked to above. This build can run on .NET v4 and if anyone's interested I can detail how to do this; "most" people shouldn't worry about this though. As usual there are two ways to get it: You can download it directly here: DO NOT link directly to this file. Please link to this page instead. http://www.getpaint....eta.Install.zip Or, you can use the built-in updater to get the update. Either wait for the prompt to automatically show up within the next few days, or go to the Utilities menu and click on Check for Updates. NOTE: You must have "Also check for pre-release (beta) versions" enabled. You can do this by going to the Utilities menu, then click on Check for Updates, then click the Options button. One thing you might all appreciate is that the download size is now much smaller as a result of dropping XP SP2 support. It used to be 4.8 MB, and now it's less than 3.5 MB

If a plugin writes to the source surface, it should crash when used in Paint.NET v3.5 or later, because the memory pages are set to read-only with VirtualProtect().

I think I turned off the profile photos, I forget. We only really need avatars here; the photo just adds confusion (it confused me, in fact).

No violence allowed on the forum!

Have you tried rebooting? The 3.5.5 Beta that I posted has some known issues where it isn't handling that correctly. (Nothing bad is resulting, like a corrupt system or anything. It's just confusing and bizarre.)

No. Paint.NET doesn't use LUA. I think there's a LUA for .NET compiler, but ultimately I don't think that's what you're thinking of.

1) I removed this beta from the auto-updater for now. 2) It'll be fine.

kitty_love, if you hate the forums so much then you can close your browser. We are not so tolerant of grumpy indignation towards things we give away for free. If you can't say something nice then don't say anything at all.

As I said before, stay tuned. This build should already be considered hopelessly out of date.

I don't make engineering decisions based on how scared an individual is of change. .NET 4 won't "damage" anything. That's just silly.

Gee. Thanks.

Link to the article itself?

Crash logs? Those are not normal.

Stay tuned.

No email notification problems here.

The original thread was locked partially because all the feedback that's necessary has already been collected. Thanks. Closed

Looks like the .NET v4 deployment story is worse than I thought. I may have to hold off on using .NET 4 for awhile. Stay tuned.

I'm hoping to find a way out of reboots, but I can't promise anything. I want the experience to be the same as it was with PDN 3.5 + .NET 3.5 SP1. That is, you could install the whole thing and only have to reboot at the very end (if necessary).

Oh, also, if you have a pending reboot -- which is quite possible since yesterday was Windows Update's "Patch Tuesday" -- you will need to reboot before installing.

Ok I've reproduced this. The crux of the issue is that .NET v4 (usually?) requires a reboot after installation. So for now, reboot and try again.

So the first time, it installed .NET 4 ... but that's as far as it went. When you run it a second time it does install Paint.NET v3.5.5. Is that correct? If you restart and then run the installer, does it all work?

What version of Windows are you all using?

As in, it didn't start? Even if you gave it a minute or so? (sometimes the hard drive can get busy so it delays the next installer for a bit)

Leif, that should not be necessary. It always picks up with Paint.NET on every system I've been working with.

It's not. Notice how I said that way back in 2007. It is not relevant anymore.