Archive for the ‘Prism’ Category
Posted by jpluimers on 2010/08/31
While writing this blog entry, I’m installing my new copy of Delphi XE (formerly called Delphi 2011 by some people).
Delphi XE and RAD Studio XE got RTM today, and are now available for purchase.
Contact my colleague Gwan Tan if you want to order it from Dutch speaking countries, and Thorsten Nannen if you want to order it from German speaking countries. Read the rest of this entry »
Posted in .NET, Delphi, Delphi for PHP, Delphi XE, Development, Prism, Software Development | 9 Comments »
Posted by jpluimers on 2010/08/20
When you write .NET 4 software, you want to deploy it to your clients, so they need to install the .NET Framework 4.
On fully patched Windows Server 2003 x86 installations, the (optional) Windows Update for Microsoft .NET Framework 4 for Windows Server 2003 x86 (KB982671) usually results in this error:
Installation Failure
Error Code: 0x80246002
Try to install the update again, or request help from one of the following resources.
It fails during download, so it does not even reach the install phase.
Don’t loose too much time resolving this: The usual solution for 0x80246002 as described in KB958056 does not work.
The systems affected don’t have anti-virus or similar software installed, so disabling those won’t work: there is nothing to disable.
What does work is the suggestion a bit lower in the 0x80246002 update fails search results Read the rest of this entry »
Posted in .NET, Delphi, Development, Power User, Prism, Software Development | 8 Comments »
Posted by jpluimers on 2010/06/17
When you do some maintenance on old projects, you sometimes bump into things you have completely forgotten about.
This time it is in Visual Studio 2005, with a WPF app, and messages about App.xml.
Since there are few threads covering this problem, so I’m not sure how many people bump into this.
I know that the problem does not limit itself to C#; I have seen people in VB.NET and Delphi.net bump into this as well.
This problem is not limited to Visual Studio 2005, some people also have it in Visual Studio 2010.
Some people also have it with other objects than App.xaml (like Windows1.xaml, etc).
If you get this error, the solution is simple:
- perform a “Clean Solution”,
- then run your app again.
This trick has worked for me every time I bumped into it. Read the rest of this entry »
Posted in .NET, C#, Delphi, Development, Prism, Software Development, Visual Studio and tools, WPF | 2 Comments »
Posted by jpluimers on 2010/05/21
Scott Dorman udpated his macro to change the target framework version for all projects in a solution to Visual Studio 2010 and published the new macro on CodeProject.
His new macro now supports these target frameworks:
Notes:
- The links are to the download pages of the frameworks; look for “Standalone version” or “Full installer” for non-bootstrap download.
(version 1.1 can be downloaded here, but is not supported in VS2010)
- The “Client Profile” versions are stripped down versions of their “Full” counterpart.
–jeroen
Posted in .NET, C#, C# 2.0, C# 3.0, C# 4.0, Delphi, Development, Prism, Software Development, Visual Studio and tools | 2 Comments »
Posted by jpluimers on 2010/05/14
I always tend to recompile assemblies when something changes they depend upon.
But now I’m even more careful after reading Fabulous Adventures In Coding : Putting a base in the middle.
Especially his checklist is important.
When you use a newer version of an assembly you depend on:
(1) at the very least test your derived types with the new base type — your derived types are relying on the mechanisms of the base types; when a mechanism changes, you have to re-test the code which relies upon that mechanism.
(2) if there was a breaking change, recompile, re-test and re-ship the derived type. And
(3) you might be surprised by what is a breaking change; adding a new override can potentially be a breaking change in some rare cases.
–jeroen
Posted in .NET, C#, C# 2.0, C# 3.0, C# 4.0, Delphi, Development, Prism, Software Development | Leave a Comment »
Posted by jpluimers on 2010/04/28
The Microsoft patterns & practices Developer Center released the Microsoft Enterprise Library 5.0 last week.
This version of the Enterprise Library has a ton of new features, and now has full support for .NET 4.0 and Visual Studio 2010.
Next to using it from C#/VB.NET, I’m looking forward to see how well this can be used from the upcoming Delphi Prism 2011 release (scheduled to be released on May 15th).
Lots of stuff to experiment with :-)
–jeroen
Posted in .NET, C# 4.0, Delphi, Development, Prism, Software Development | Leave a Comment »
Posted by jpluimers on 2010/04/27
If you have a TechNet or MSDN account, you can download the SharePoint, Office, Visio and Project 2010 RTM builds.
Downloads have become available on April 23rd.
The SharePoint designer is available from the Microsoft Download centre as William Conrwill describes at CodeJedi.NET : SharePoint, Office, Visio and Project 2010 RTM are now available on MSDN.
If you have SA, then as of today (April 27), you can get your volume licenses as well.
William describes more dates in his post Office, SharePoint, Project and Visio 2010 have made RTM!
I’ll be busy playing with all the bits from Delphi and .NET API perspective :-)
–jeroen
Posted in .NET, Delphi, Development, Power User, Prism, Software Development | Leave a Comment »
Posted by jpluimers on 2010/04/22
I usually pick a fresh VM for installing an RTM build, but if you have loads of stuff on your (physical) machine, upgrading RC to RTM can be a real time saver.
Stack Overflow has a nice question Upgrading Visual Studio 2010 RC to RTM answered by Danny Thorpe (yes, two links: blog / wikipedia).
The order is really imporant, so lets repeat that here:
- Uninstall all the VS 2010 parts
- Uninstall the .NET Framework Multitarget package.
- Reboot
- Uninstall the .NET Framework client package
- Reboot
–jeroen
Posted in .NET, C#, C# 4.0, Delphi, Development, Prism, Software Development, Visual Studio and tools | Leave a Comment »
Posted by jpluimers on 2010/04/14
Every major release of software will bring great new stuff, but the price of upgrading from a previous version is that some stuff will break.
.NET 4.0 brings a lot of nice stuff as well, but there are a few things that break.
There is a nice Breaking changes in .NET 4.0 – Stack Overflow article on this.
The article is now a community wiki, and refers to these pages:
Since the article is a community wiki, expect it to be updated over time.
I wonder what these changes will bring (and break) in the upcoming Delphi Prism release (the datasheet is out now, the product should be out before the end of may).
–jeroen
PS:
If you do not have an MSDN subscription, but still want to see if things break for you, try one of these:
Scott Guthrie has a nice post on the bells and whistles of VS2010.
Posted in .NET, ASP.NET, C#, C# 4.0, Delphi, Development, Prism, Software Development, Visual Studio and tools, Web Development | 1 Comment »
Posted by jpluimers on 2010/02/12
Google published an interesting graph generated from their internal data based on their indexed web pages.
A quick summary of popular encodings based on the graph:
- Unicode – almost 50% and rapidly rising
- ASCII – 20% and falling
- Western European* – 20% and falling
- Rest – 10% and falling
Conclusion: if you do something with the web, make sure you support Unicode.
When you are using Delphi, and need help with transitioning to Unicode: contact me.
–jeroen
* Western European encodings: Windows-1252, ISO-8859-1 and ISO-8859-15.
Reference: Official Google Blog: Unicode nearing 50% of the web.
Edit: 20100212T1500
Some people mentioned (either in the comments or otherwise) that a some sites pretend they emit Unicode, but in fact they don’t.
This doesn’t relieve you from making sure you support Unicode: Don’t pretend you support Unicode, but do it properly!
Examples of bad support for Unicode are not limited to the visible web, but also applications talking to the web, and to webservices (one of my own experiences is explained in StUF – receiving data from a provider where UTF-8 is in fact ISO-8859: it shows an example where a vendor does Unicode support really wrong).
So: when you support Unicode, support it properly.
–jeroen
Posted in .NET, ASP.NET, C#, Database Development, Delphi, Development, Encoding, Firebird, IIS, InterBase, ISO-8859, ISO8859, Prism, SOAP/WebServices, Software Development, SQL Server, Unicode, UTF-8, UTF8, Visual Studio and tools, Web Development | 7 Comments »