Archive for the ‘Software Development’ Category
Posted by jpluimers on 2016/02/16
When you own the full stack:
virtual machine (Build 201602)
These installs contain:
Windows 10 Enterprise Evaluation, Version 1511
Visual Studio 2015 Community Update 1
Windows developer SDK and tools (Build 10586)
Windows IoT Core SDK and Raspberry Pi 2 (Build 10586.0.151029-1700)
Windows IoT Core project templates (Version 1.0)
Microsoft Azure SDK for .NET (Build 2.8.2)
Windows Bridge for iOS (Build 0.1.0.160114)
Windows UWP samples (Build 2.0.4)Windows Bridge for iOS samples
The VMware VM link redirects to https://windowsdeveloper.azureedge.net/vm-1602/Win10Eval_1602_VMware.zip
Also available for Hyper-V , VirtualBox , Parallels
–jeroen
Source: Get a Windows 10 development environment – Windows app development
Posted in .NET , .NET 4.5 , C# , C# 5.0 , C# 6 (Roslyn) , Cloud Development , Development , Hardware Development , Raspberry Pi , Software Development , VB.NET , VB.NET 14.0 , Visual Studio 2015 , Visual Studio and tools , Windows Azure | Leave a Comment »
Posted by jpluimers on 2016/02/16
This was very useful to get a WebClient with a WebProxy configured to use a proxy server that is based on NTLM authentication.
The note in the MSDN NTLM and Kerberos Authentication . documentation however was totally wrong.
String MyURI = "http://www.contoso.com/";
WebRequest WReq = WebRequest.Create MyURI;
WReq.Credentials = CredentialCache.DefaultCredentials;
Note NTLM authentication does not work through a proxy server.
This code works perfectly fine as the CredentialsCache.DefaultCredentials contains your NTLM or Kerberos credentials .
It even works when you have a local Fiddler http proxy as a facade in front of your NTLM proxy.
Read the rest of this entry »
Posted in .NET , .NET 2.0 , .NET 3.0 , .NET 3.5 , .NET 4.0 , .NET 4.5 , C# , C# 2.0 , C# 3.0 , C# 4.0 , C# 5.0 , C# 6 (Roslyn) , Development , Fiddler , Software Development , Web Development | Leave a Comment »
Posted by jpluimers on 2016/02/14
Now that you’re 21 , have a glass of wine and watch this great presentation by Warren Postma which he made for last years birthday:
VIDEO
–jeroen
Posted in Delphi , Delphi 1 , Delphi 2 , Delphi 2005 , Delphi 2006 , Delphi 2007 , Delphi 2009 , Delphi 2010 , Delphi 3 , Delphi 4 , Delphi 5 , Delphi 6 , Delphi 7 , Delphi 8 , Delphi x64 , Delphi XE , Delphi XE2 , Delphi XE3 , Delphi XE4 , Delphi XE5 , Delphi XE6 , Delphi XE7 , Delphi XE8 , Development , Software Development | Leave a Comment »
Posted by jpluimers on 2016/02/13
Seems they got only released just yesterday because of the QA effort taking a long time. But it’s good news for Delphi/Rad Studio/C++-Builder Update Subscription members: some fixes are now back-ported to 2 Delphi versions. Which is a new milestone in support from Embarcadero.
Anyway: BLDN .
Note that the list of fixes is at the bottom of these pages:
Source: RAD Studio Hotfixes for XE8 and XE7 with 10 Seattle fixes
I also found out that I never updated the links for XE8 update 1 downloads (I did the original XE8 links Delphi XE8 is out with version 22.0.19027.8951; Spring4D is almost ready. « The Wiert Corner – irregular stream of stuff ) so there they are:
–jeroen
Posted in Delphi , Delphi 10 Seattle , Delphi XE7 , Delphi XE8 , Development , Software Development | 2 Comments »
Posted by jpluimers on 2016/02/12
For a short while (from Windows 2003 Service Pack 1 till Windows 2003 service pack 2) some updates used Windows Hotpatching.
Some links on the how/why and how to abuse it:
All because of this little post:
Hier ein Einblick in die Denkweise von Leuten, die Software auf CD-ROM verteilen und bei denen Release Zyklen in Monaten und nicht Minuten gemessen werd… – Kristian Köhntopp – Google+
–jeroen
Posted in C , Development , History , Software Development , The Old New Thing , Windows Development | Leave a Comment »
Posted by jpluimers on 2016/02/11
Thanks Oliver for sumarising this: Translation Memory Tools Tried and Found Wanting – Oli’s Blog
His conclusion support why I see all my clients building their own translation tooling: no 3rd party tool really supports the full process well, especially not the translation memory parts.
–jeroen
Posted in Development , internatiolanization (i18n) and localization (l10) , Software Development | Leave a Comment »
Posted by jpluimers on 2016/02/10
Thanks User Josh Close – Stack Overflow . for answering the below on Stack Overflow: it got my Resharper Alt-Enter key workign again.
Re-apply Visual Studio keyboard scheme:
(VS2013 latest ReSharper)
ReSharper > Options > Environment > Keyboard & Menus > ReSharper Platform keyboard scheme: Visual Studio > Apply Scheme > Save.
This will reset the shortcut keys for ReSharper.
(older versions)
ReSharper > Options > Environment > General > Visual Studio Integration > Apply
–jeroen
via: visual studio – Resharper Alt Enter not working – Stack Overflow .
Posted in .NET , C# , Development , Keyboards and Keyboard Shortcuts , Power User , Software Development , Visual Studio 2013 , Visual Studio and tools | Leave a Comment »
Posted by jpluimers on 2016/02/09
Interview with by Andrew Hunt and David Thomas, the authors of The Pragmatic Programmer: From Journeyman to Master .
Many interesting quotes including:
Most people take DRY to mean you shouldn’t duplicate code. That’s not its intention. The idea behind DRY is far grander than that.
–jeroen
via Orthogonality and the DRY Principle .
Posted in Agile , Development , DRY , Software Development | Leave a Comment »
Posted by jpluimers on 2016/02/04
I wrote about this before , named it a cardinal sin too, but I seem to have to repeat this:
When your product thinks the license is validate and quits without allowing the customer to save its work, then you’ve committed a cardinal sin.
Yes, I can talk about cardinal sins : I’ve been named after the artist Hieronymus Bosch (:
For me it is OK if a product checks for binaries that do not to the product (and not signed by the vendor) in the product directories and fails to start, or to present a nag screen that takes a while to disappear, or even to limit functionality.
But:
The product should always tell why the license check failed.
The product never can force the customer to loose work.
The documentation should show failure situations (not just the OK counterparts ).
Given some recent posts and the fact that over the course of 10 different versions I lost days of work and at conferences I usually get multiple questions from people having suffered from this, I really had to bring this up again.
Read the rest of this entry »
Posted in Delphi , Development , Licensing , Software Development | 7 Comments »