|
Hmm. I define my 'resource' strings in my XAML:
<ResourceDictionary xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
xmlns:s="clr-namespace:System;assembly=mscorlib">
<s:String x:Key="Name" x:Uid="Name">Thing name</s:String>
...My localization gizmo assumes everything translatable lives there.
Software Zen: delete this;
|
|
|
|
|
Is it safe to assume that you rolled your own localization tool, rather than use the ones that come with the framework?
David A. Gray
Delivering Solutions for the Ages, One Problem at a Time
Interpreting the Fundamental Principle of Tabular Reporting
|
|
|
|
|
I know it sounds like a bad case of not-invented-here, but we're stuck on VS2008. Back then, the only 'tool' available was a sample program called LocBaml. It used .NET facilities to traverse compiled XAML (aka BAML) and produce translated resource DLL's. Unfortunately LocBaml wasn't very capable and didn't handle a lot of cases. Fortunately the source code for LocBaml was provided.
I wrote my own tool to handle LocBaml's missing cases and to provide a better persistence format for translators. It also handles the typical use-case of updating an existing translation to new code, which LocBaml did not.
Software Zen: delete this;
|
|
|
|
|
No, it sounds more like the work of a resourceful engineer. Good on you! 
David A. Gray
Delivering Solutions for the Ages, One Problem at a Time
Interpreting the Fundamental Principle of Tabular Reporting
|
|
|
|
|
The core features of the WizardWrx .NET API are now available as a set of NuGet packages. Thanks to the dependency chain, you can get all of them in one go by installing the WizardWrx.Core library, found at https://www.nuget.org/packages/WizardWrx.Core/. Otherwise, search for "WizardWrx" to see the list. Since they rely on the existing library documentation at WizardWrx .NET API, the documentation included with the packages is scant. However, each package includes a ReadMe file that points to the real documentation, which is MSDN-style documentation generated by DocFX. The ReadMe opens in Visual Studio when the installation completes, and the package includes a Markdown copy in addition to the text file that displays in Visual Studio.
The WizardWrx .NET API is a set of libraries that expose a rich set of general-purpose helper classes for use in projects that target the Microsoft .NET Framework. Among other things, they offer the following.
1) Syntactic sugar, such as the routines that identify the first, last, and next-to-last iteration of a FOR loop, convert subscripts to and from ordinals (zero-based versus one-based subscripts), compute a modulus (remainder), and perform decimal shifts
2) Prse dynamically generated format control strings (used with string.format and such),
3) Reduce computing message digests to a single method call
4) Transparently convert Registry values of all types into native types (strings, integers of various sizes, and byte arrays)
5) Parse command line arguments for any program (command line or graphical),
6) Add numerous extension methods to system.string and system.IO.FileOnfo
7) Simplify working with the match groups returned by the Regular Expression engine
8) Dynamically generate format strings to compactly represent data in tabular format
9) Implement the Singleton design pattern in a way that fully leverages certain guarantees about the behavior of static constructors
10) Format and log exception reports, optionally recording them in a Windows Event Log and efficiently reporting them on the two standard console output streams, taking into account when either or both has been redirected to a file
11) Accurately identify the type of processor on which the code is executing and the Windows subsystem (character mode, graphical, etc.) in which it is executing
12) Walk the dependency tree of any executing assembly
13) Sort collections of FileInfo objects, so that the files they represent can be processed in any order
14) Provide scores of handy symbolic constants to disambiguate and properly document your code
The3re is much more; these are the highlights, most of which I use daily.
David A. Gray
Delivering Solutions for the Ages, One Problem at a Time
Interpreting the Fundamental Principle of Tabular Reporting
modified 4-May-19 2:57am.
|
|
|
|
|
|
No idea, but the documentation sure looks fine 
|
|
|
|
|
WizardWrx is a business name under which I operated as an independent software engineer for a number of years. My wife suggested it as a way to convey that she sees me as a wizard, in the magician sense, of software engineering. At the time, we also happened to be living in a village called Wizard Wells.
David A. Gray
Delivering Solutions for the Ages, One Problem at a Time
Interpreting the Fundamental Principle of Tabular Reporting
|
|
|
|
|
|
Quote: All Right Then, Keep Your Secrets - Frodo Baggins - YouTube[^]
Pardon?
David A. Gray
Delivering Solutions for the Ages, One Problem at a Time
Interpreting the Fundamental Principle of Tabular Reporting
|
|
|
|
|
What we really want to know is what the purpose of your library is ! 
|
|
|
|
|
Please accept my apology for the oversight. I've significantly improved the original message.
David A. Gray
Delivering Solutions for the Ages, One Problem at a Time
Interpreting the Fundamental Principle of Tabular Reporting
|
|
|
|
|
Thanks, much clearer now
Btw. I'm still using SandCastle but you pointed me to DocFX which looks very interesting !
|
|
|
|
|
Several years ago, I considered implementing Sandcastle, but I never became sufficiently motivated to make it happen. By the time I became so motivated, it was evident that the momentum was shifting in favor of DocFX. If you are serious about using it, you might want to read How To Integrate DocFX API Documentation Into Your GitHub Repository, which describes the lessons I learned during my implementation. I've been using it long enough now that it "just works."
David A. Gray
Delivering Solutions for the Ages, One Problem at a Time
Interpreting the Fundamental Principle of Tabular Reporting
|
|
|
|
|
|
For what it's worth, since DocFX generates static HTML pages, you can host them anywhere.
David A. Gray
Delivering Solutions for the Ages, One Problem at a Time
Interpreting the Fundamental Principle of Tabular Reporting
|
|
|
|
|
Found a typo:
Quote: suzh as 1 and l
What the heck is this thing anyways?
Latest Article - A 4-Stack rPI Cluster with WiFi-Ethernet Bridging
Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
Artificial intelligence is the only remedy for natural stupidity. - CDP1802
|
|
|
|
|
David updated his information, see above
|
|
|
|
|
What happens if everybody tries to push their "product" here like this?
It does not solve my Problem, but it answers my question
modified 19-Jan-21 21:04pm.
|
|
|
|
|
I've made one announcement. Other than answering questions, that's all you'll see from me. BTW, it's also free to all comers. There's already been a minor update since I wrote the original message, which would have gone without mention, had I not wanted to reply to this message.
David A. Gray
Delivering Solutions for the Ages, One Problem at a Time
Interpreting the Fundamental Principle of Tabular Reporting
|
|
|
|
|
I think the point he was making was that this forum isn't really intended for posting announcements of software releases or package updates. Instead, have you considered writing an article, tip or blog post to highlight your software and give some background on it and it's usage?
As per the forum description at the top of the page:
The Weird and The Wonderful forum is a place to post Coding Horrors, Worst Practices, and the occasional flash of brilliance.
|
|
|
|
|
Yep. Point taken, and I've found a more appropriate forum for it.
David A. Gray
Delivering Solutions for the Ages, One Problem at a Time
Interpreting the Fundamental Principle of Tabular Reporting
|
|
|
|
|
The https://github.com/txwizard/WizardWrx_NET_API is now at version 7.15, with one subtle bug smashed flat and a few interesting, but obscure changes. As always full documentation is at https://txwizard.github.io/WizardWrx_NET_API/.
What makes this especially interesting is the way the bug that motivated this update came to the surface; it appeared in the output dumped into the Visual Studio debugger window of an application that consumed it.
Numerous distractions interfered with finishing the repair. The event that pushed me to finish it was a very minor addition that I needed to make to WizardWrx.Common.dll, one of three libraries that underpin the whole API. The common library is composed almost entirely of constants, to which I needed to add a few new ones so that I can use them as building blocks from which to build other string constants. Though all of them were already defined as character constants, you cannot mix character and string constants in the definition of a new string constant.
The WizardWrx .NET API is a set of libraries that expose a rich set of general-purpose helper classes for use in projects that target the Microsoft .NET Framework. Among other things, they offer the following.
1) Syntactic sugar, such as the routines that identify the first, last, and next-to-last iteration of a FOR loop, convert subscripts to and from ordinals (zero-based versus one-based subscripts), compute a modulus (remainder), and perform decimal shifts
2) Prse dynamically generated format control strings (used with string.format and such),
3) Reduce computing message digests to a single method call
4) Transparently convert Registry values of all types into native types (strings, integers of various sizes, and byte arrays)
5) Parse command line arguments for any program (command line or graphical),
6) Add numerous extension methods to system.string and system.IO.FileOnfo
7) Simplify working with the match groups returned by the Regular Expression engine
8) Dynamically generate format strings to compactly represent data in tabular format
9) Implement the Singleton design pattern in a way that fully leverages certain guarantees about the behavior of static constructors
10) Format and log exception reports, optionally recording them in a Windows Event Log and efficiently reporting them on the two standard console output streams, taking into account when either or both has been redirected to a file
11) Accurately identify the type of processor on which the code is executing and the Windows subsystem (character mode, graphical, etc.) in which it is executing
12) Walk the dependency tree of any executing assembly
13) Sort collections of FileInfo objects, so that the files they represent can be processed in any order
14) Provide scores of handy symbolic constants to disambiguate and properly document your code
The3re is much more; these are the highlights, most of which I use daily.
David A. Gray
Delivering Solutions for the Ages, One Problem at a Time
Interpreting the Fundamental Principle of Tabular Reporting
modified 4-May-19 3:09am.
|
|
|
|
|
Upon trying to log into one of my favorite sites this morning:
ErrorCode 9002
Message [Macromedia][SQLServer JDBC Driver][SQLServer]The transaction log for database 'irongate' is full due to 'LOG_BACKUP'.
SQLState HY000
|
|
|
|
|
At least they gave you a descriptive, detailed error message! 
"Go forth into the source" - Neal Morse
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
