Archive for the ‘Development’ Category
Posted by jpluimers on 2013/07/23
Ever since I started .NET programming after .NET Beta 1 Arrived in 2001, I found that many people struggle with the relation between assemblies and namespaces.
So I was glad that I posted this answer about 2.5 years ago on StackOverflow. Below is the slightly edited form:
People are easily confused by the namespace/assembly thing, as it decouples the concept of where your code is physically located (the assembly) and how you reference it:
- logically reference is by using the namespace
- physical reference is by referencing the assembly
I usually explain the relation using the word contribute:
- An assembly can contribute to multiple namespaces.
For instance, the System.Data.dll assembly contributes to namespaces like System.Data (e.g. the class System.Data.DataTable) and Microsoft.SqlServer.Server (e.g. the class Microsoft.SqlServer.Server.SqlContext).
- Multiple assemblies can contribute to a single namespace.
For instance both the System.Data.dll assembly and the System.Xml.dll assembly contribute to the System.Xml namespace.
Which means that if you use the System.Xml.XmlDataDocument class from your project, you need to reference the System.Data.dll assembly.
And if you use the System.Xml.XmlDocument class, you need to reference the System.Xml.dll from your project.
(the above examples are .NET 4.0, but likely hold for previous .NET versions as well).
Danny Thorpe explained the concept of namespace and internal really well, so I won’t go into detail about those.
Ever since I started .NET courses 10 years ago, I draw a table explaining assemblies and namespaces like this:
–jeroen
via: C# assemblies, whats in an assembly? – Stack Overflow.
Posted in .NET, .NET 1.x, .NET 2.0, .NET 3.0, .NET 3.5, .NET 4.0, .NET 4.5, .NET CF, C#, C# 1.0, C# 2.0, C# 3.0, C# 4.0, C# 5.0, Development, Software Development | Leave a Comment »
Posted by jpluimers on 2013/07/20
Bitsavers published 2 new Logitech PDFs:
Who didn’t have a Logitech mouse back then?
I had the C7, various MouseMans, and a few more modern mice. Why not all mice? I developed RSI in the DOS era, ending up with TrackPoints and more recently Apple touchpads)
I remember the Logimouse C7, not because it was from Logitech, but because it was available from so may OEMs. Long before Logitech built OEM mice for Apple, they were founded in Apples, Swizerland.
The cool thing: the Programmers Toolkit had examples in Modula-2. I used that as a base to write quite some Turbo Pascal code for mouse handing.
Oh: Bitsavers does have a Logitech Modula-2 PDF online too for quite some time. I mentioned that in More Old Micro Cornucopia issues on BitSavers from 1987 and 1988.
–jeroen
via: Bitsavers’ Index of /pdf/logitech.
Posted in BitSavers.org, Development, History, Pascal, Power User, RSI, Software Development, Turbo Pascal | Tagged: c7, cornucopia, logitech mouse, modula 2 | Leave a Comment »
Posted by jpluimers on 2013/07/18
I bumped into the below answer that I gave a while (what is 4 years in a developer’s life ) on StackOverflow.
It is about Delphi Design Patterns. Sepcifically the Factory Pattern, and explains how virtual constructors implement it.
They are one of the 3 corner stones on which the component based Delphi form designer and object inspector are built:
- Virtual constructors
- Properties (events are just a special form of property)
- Run-Time Type Information.
So here it goes: Read the rest of this entry »
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 XE, Delphi XE2, Delphi XE3, Delphi XE4, Development, Software Development | 6 Comments »
Posted by jpluimers on 2013/07/18
A while ago, I wrote about .NET/C# duh moment of the day: “A char can be implicitly converted to ushort, int, uint, long, ulong, float, double, or decimal (not the other way around; implicit != implicit)”.
There is another duh moment having to do with the various C# operators like += which is being described as being
a += b
is equivalent to
a = a + b
You might think that this also holds:
a += b + c
is equivalent to
a = (a + b) + c
But Eric Lippert has explained this is not the case: it is equivalent to:
a = a + (b + c)
In his explanation, he also shows the confusion can get you very surprising results if you mix string, chars and ints in the expression: depending on the statement and ordering, you either concatenate characters, or add ints to characters.
He also recommends you should not do concatenation: either use String.Format, or StringBuilder. I totally agree with that.
Recommended reading!
–jeroen
Posted in .NET, C#, C# 1.0, C# 2.0, C# 3.0, C# 4.0, C# 5.0, Development, Software Development | Leave a Comment »
Posted by jpluimers on 2013/07/17
2 more issues got on-line both close to a 100 pages each:
So the only issues missing are #28, #30 and #31.
–jeroen
via: More Old Micro Cornucopia issues on BitSavers from 1987 and 1988 « The Wiert Corner – irregular stream of stuff.
Posted in Assembly Language, BitSavers.org, C, C++, Development, History, Pascal, Software Development, Turbo Pascal, Turbo Prolog, x86 | Tagged: Media, technology | 1 Comment »
Posted by jpluimers on 2013/07/17
I still see a truckload of projects that connect to SQL Server do this using OLE DB or the Native SQL Client.
All OLE DB access to SQL Server has been deprecated, not only from regular access, but also from SSIS.
These are the only ways you should connect to SQL Server:
- SqlClient (managed code)
- JDBC (Java)
- ODBC (for native code)
For instance, these have been deprecated (for each one, I linked to the oldest SQL Server version where they were made available for):
- SQLOLEDB
- SQLNCLI
- SQLNCLI10
- SQLNCLI11
- SQLXMLOLEDB.3.0
- SQLXMLOLEDB.4.0
–jeroen
via: RIP OLE DB.
Posted in Database Development, Development, SQL Server | Leave a Comment »
Posted by jpluimers on 2013/07/11
Don’t increase your Windows Timer Resolution. And keep an eye on programs that do:
Raising the Windows timer frequency is bad. It wastes power and makes your computer slower. Routinely doing this in all sorts of programs that end up sitting idle for hours really needs to stop.
You can use ClockRes to monitor the time resolution and what programs changed it.
–jeroen
via: Windows Timer Resolution: Megawatts Wasted | Random ASCII.
Posted in .NET, Development, Opinions, Pingback, Power User, Software Development, WPF | Tagged: computer, software, technology, timer resolution | Leave a Comment »
Posted by jpluimers on 2013/07/11
Josh Stodola wrote a nice answer on the Determine .NET Framework version for dll – Stack Overflow question for using ILDASM to show the required .NET Framework/CLR version for an assembly.
From that, I wrote this tiny batch file:
ildasm.exe %1 /metadata[=MDHEADER] /text /noil | find "Metadata section:"
It gives output like this:
ildasm.exe C:\Windows\Microsoft.NET\Framework\v4.0.30319\System.XML.dll /metadata[=MDHEADER] /text /noil | find "Metadata section:"
// Metadata section: 0x424a5342, version: 1.1, extra: 0, version len: 12, version: v4.0.30319
The cool thing is that older ILDASM versions work on assemblies requiring newer .NET Frameworks/CLRs.
So it is relatively future proof.
–jeroen
Posted in .NET, .NET 1.x, .NET 2.0, .NET 3.0, .NET 3.5, .NET 4.0, .NET 4.5, C#, C# 1.0, C# 2.0, C# 3.0, C# 4.0, C# 5.0, Development, Software Development | Leave a Comment »
The Wiert Corner - irregular stream of stuff 