Comments for PreEmptive Solutions

Comment on Dotfuscator and MSBuild by ion Singh

ion Singh — Fri, 28 Oct 2011 04:23:13 +0000

Does this work with xap wp7 packages?

Comment on The new WP7 App Hub reporting is great – and it’s even better with analytics! by Steven Walsh

Steven Walsh — Sat, 22 Oct 2011 16:45:39 +0000

Sorry — this is a question not directly related to this post. I was wondering if anything from your talk last Thursday for the NYC .NET group was available online.

Thanks,
Steve

Comment on Jumping into the Clouds by Administrate

Administrate — Wed, 04 May 2011 14:37:06 +0000

Events Post…

Event software stories to enjoy….

Comment on Notes from the RSA Conference by bradyliu

bradyliu — Tue, 29 Jun 2010 09:04:31 +0000

com.preemptive.dasho.DashOException:NO input classes. how to deal? thanks!

Comment on Launch of Visual Studio 2010 & Dotfuscator CE 5 by Joe Kuemerle

Joe Kuemerle — Tue, 11 May 2010 19:00:09 +0000

Pedro,

To follow up, PreEmptive has officially stated that the PreEmptive.Attributes.dll library may be freely distributed with application source code see: http://preemptive.com/blog/archives/162 . In addition, we are providing a version of that assembly that can be included in pre-.NET 4.0 projects here: http://runtimeintelligence.codeplex.com/releases .

We understand the additional friction involved in there being no automated build solution available for open source and community projects and are currently working on ways that we can help with that as well. Keep an eye on this blog as we’ll certainly continue to talk about it here.

Thank you for your feedback.

Comment on Launch of Visual Studio 2010 & Dotfuscator CE 5 by Pedro

Pedro — Tue, 11 May 2010 13:43:28 +0000

Hi Brandon,

Thanks for your candid reply. I think your suggestion of using Dotfuscator’s UI to store the attribute preferences could work, although it is not ideal, at least for me. I like being able to do a Find in Sources in my code for all currently defined Features. In the long run, the GPL approach seems to be the best way to go.

Regarding MSBuild integration, I can certainly see its value for Pro licenses, and I’m definitely not advocating that this should be made available in CE. Instead, PreEmptive Solutions could take applications from Open Source projects in order to supply them with some sort of free license that would give that kind of support.

Just my two cents.

Thanks,
Pedro

Comment on Launch of Visual Studio 2010 & Dotfuscator CE 5 by Brandon Siegel

Brandon Siegel — Mon, 10 May 2010 15:29:31 +0000

Hi Pedro,

Thanks for your insightful comments. I’m glad to hear that you found Runtime Intelligence as easy to use as we like to think it is :) I’ve forwarded your comments to some people who I hope will be able to do something about them. You can of course do instrumentation without referencing the PreEmptive.Attributes.dll by defining your attributes in Dotfuscator’s UI (where they will be saved in your config file, which can be stored in your project’s source control repo). Obviously this is not ideal in some situations - going forward I am looking to see the code to our Attributes DLL released under a GPL-compatible license (I personally cannot see a reason not to, as it’s simply a bunch of attribute definitions). As far as build integration, I cannot predict where we will go with that. I’d personally like to see at least command-line support added to CE, but the powers that be certainly see build integration as a motivator for Dotfuscator Pro purchases. We as a company are committed to open source, and I have been and will continue to make sure that open source developers have the tools they need, cost-free and under compatible licensing, in order to help their software succeed.

Comment on Launch of Visual Studio 2010 & Dotfuscator CE 5 by Pedro

Pedro — Sun, 09 May 2010 00:03:10 +0000

I think the product has great potential, and the CodePlex/PreEmptive partnership could become a great story. However, for that to happen for anything other than the simplest of projects, a couple of things would need to happen:
- Serious open source projects use some kind of automated build, which will not work with PreEmptive because the MSBuild task is only available for Pro licenses.
- The attributes that are required in the source code (unless someone would ever want to edit those values in the UI every time the software is to be released) depend on a PreEmptive-owned DLL that cannot be redistributed. As such, the Open Source project owner cannot upload the DLL to the project source code repository.

These two situations will make the proposition a deal breaker, which is a shame, considering the benefit that Open Source projects could reap with little effort (I have completed that effort for Scrum Sprint Monitor, but now I have my hands tied with this situation).

Best regards,
Pedro

Comment on Launch of Visual Studio 2010 & Dotfuscator CE 5 by Brandon Siegel

Brandon Siegel — Wed, 28 Apr 2010 14:39:52 +0000

I recommend you uninstall Dotfuscator CE, and then delete the folder C:\Users\\AppData\Local\PreEmptive Solutions\Dotfuscator Community Edition (for Vista / Win7) or C:\Documents and Settings\\Local Settings\Application Data\PreEmptive Solutions\Dotfuscator Community Edition (for Windows XP). Once this is done, you can safely re-install Dotfuscator CE.

If this does not get you going, please open a thread on our forums at http://www.preemptive.com/forum/

Comment on Launch of Visual Studio 2010 & Dotfuscator CE 5 by jasonsi

jasonsi — Wed, 28 Apr 2010 08:39:58 +0000

I run a problem when using Dotfuscator CE 5.0.2300, which was installed along with VS2010 RTM.

It worked fine before, until a power cut happened when the dotfucator was running. When the power restored, I can’t launch the dotfuscator.exe anymore. Double clicking the dotfuscator.exe, nothing happen, there is no message. Tring launch it from VS2010 doesn’t help.

I uninstalled the Dotfuscator and installed it, or even uninstalled the VS2010 and re-install, no improvement.

Anyone has any idea why this happens? What should I do then? I’ve spent 5 hours on this problem.