Build with .NET Framework 2.0

SyntaxEditor for Windows Forms Forum

Posted 14 years ago by Mac
Avatar
Hi,

Can you, please, provide us with SyntaxEditor build under .NET Framework 2.0?
Now it refers with 1.0 system assemblies, such as System.Windows.Forms.dll.
And when we use Dotfuscator for VS.NET 2005 on host where .NET Framework 2.0 only installed it can not obfuscate project. As workaround we can install .NET Framework 1.0 but after VS.NET 2005 release we want to forget .NET Framework 1.* :-)

Thanks.

Comments (17)

Posted 14 years ago by Actipro Software Support - Cleveland, OH, USA
Avatar
Yes we would like to provide new builds of our controls in the RTM 2.0 framework. One thing we have to do first though is update our Shared/WinUICore libraries to use some of the new 2.0 features. We've started doing this and are currently evaluating the best way to do the project structuring and builds.


Actipro Software Support

Posted 14 years ago by Mac
Avatar
If you have already C# and VB.NET 2.0 (new keywords: partial, global etc.) languages syntax highlighting XML files?


If so, where I can download it?
Posted 14 years ago by Actipro Software Support - Cleveland, OH, USA
Avatar
Hi Mac,

We don't have the definitions updated yet. This might not make the next maintenance release but hopefully will the one after that.


Actipro Software Support

Posted 14 years ago by Actipro Software Support - Cleveland, OH, USA
Avatar
The language definitions have been updated for the 2.0 keywords. This will appear in the upcoming maintenance release.


Actipro Software Support

Posted 14 years ago by Actipro Software Support - Cleveland, OH, USA
Avatar
The language definitions have been updated for the 2.0 keywords. This will appear in the upcoming maintenance release.


Actipro Software Support

Posted 14 years ago by Mac
Avatar
Very good news! Big thanks.
Posted 14 years ago by (Anonymous)
Avatar
I am also interested in 2.0 support. All our other vendors are very near release of 2.0 products.
Posted 14 years ago by Actipro Software Support - Cleveland, OH, USA
Avatar
Our current assemblies work fine with the .NET 2.0 framework and are fully functional in it, even though they are compiled in the 1.0 framework.

We are working on making separate native compiles under the 2.0 framework though, and are still looking at the best way to package and deploy them.


Actipro Software Support

Posted 14 years ago by (Anonymous)
Avatar
Ok. Given the way I use the editor, if it works as is in the 2.0 environment, I am good to go.
Posted 14 years ago by John Kresl
Avatar
Do you have a ballpark date when you would be converted over to the 2.0 framework?
Posted 14 years ago by Actipro Software Support - Cleveland, OH, USA
Avatar
Since all of our controls are compiled in an earlier framework but work fine in the 2.0 framework, our top priority at the moment is getting the UIStudio bar controls done.

After that, we're going to continue examining our installer options, which are upgrading InstallShield, switching to Wise, or writing a custom external UI for our installer.

Along with that we also need to convert our projects to VS 2005 format and build compiler options so that we can still support 1.0 framework builds as well as 2.0 framework builds. Ideally we'll have an environment set up where we can continue supporting both frameworks natively.

So really, this isn't too far off but I don't have a date for you.


Actipro Software Support

Posted 14 years ago by Steve Millar
Avatar
Any updated date information?
Posted 14 years ago by Actipro Software Support - Cleveland, OH, USA
Avatar
Hi Steve,

We have been playing a little with the app that takes a 2.0 project and builds a 1.1 assembly. The major hurdle right now with moving forward is how to version the assemblies. With .NET they eliminated DLL hell but now have a new versioning hell.

For instance, we have customers who want 32-bit 1.1 framework builds, 32-bit 2.0 framework builds, and 64-bit 2.0 framework builds of our products. How should we version all these different assemblies since having them have the same version number would probably cause issues if multple builds of the same version number are placed on a system.

Does anyone have any suggestions? We'd love to hear them!


Actipro Software Support

Posted 14 years ago by Robert Conde - Senior Systems Engineer, a.i. solutions
Avatar
Any update on this guys?

Robert Conde

Robert Conde

Posted 14 years ago by Actipro Software Support - Cleveland, OH, USA
Avatar
Yes we know how we want to name the assemblies going forward. We are working on our WiX installer to replace our old InstallShield-based installer. We need to try and focus more on getting that done. It's been slower than initially expected due to all the great development we've been doing for SyntaxEditor 4.0. It's tough to put that aside once we start getting on a roll like we are. :)


Actipro Software Support

Posted 14 years ago by Actipro Software Support - Cleveland, OH, USA
Avatar
We now have a ZIP available internally for SyntaxEditor that has been converted to .NET 2.0 and .NET 1.1 native compiles via our new automated build process. This ZIP will be tested a little bit more and released in the next couple weeks. However is anyone interested in giving it a shot right now? If so, send us an email.

The codebase is the same as the latest SyntaxEditor maintenance release, the only difference is the installer and separate builds targeted for .NET 2.0 and .NET 1.1.


Actipro Software Support

Posted 14 years ago by Actipro Software Support - Cleveland, OH, USA
Avatar
Hey everyone, in case you didn't get the newsletter, .NET 2.0 builds are now live in the latest maintenance release.


Actipro Software Support

The latest build of this product (v2020.1 build 0400) was released 22 days ago, which was after the last post in this thread.

Add Comment

Please log in to a validated account to post comments.