Just updated my blog to use something else than the absolutely horrible DNN basic Blog Module. Let's see how this works out...
I've just been looking at the Resources.resx file within a Solution I've inherited. It was a long project, and I can see from the contents of the resx, that things must have gone back and forth between client, BA, and developers several times. Each time, the UI text fragments getting cut up a little bit more, and pasted together in order to make other sentences -- until the whole thing, code wise, was a pot-pourri of gawd awful code such as
literalControl.Text =
Resources.MSG01
+ "
"
+ Resources.MSG13B
+ "
" + Resources.MSG52b;
There has to be a better way.
I guess the fundamental thing that is that BA's have only rudimentary tools to work with -- Excel spreadsheets -- to build up messages. Their toolset is far behind the potential that Visual Studio can accomplish.
What if we could give them more power? What if we could give them a way to define Resource strings, that contain monikers that refer to other resources?
Instead of them having to write:
MSG01 = "....";
MSG013B = "...";
just so that the developer can shove a BR or Environment.NewLine in there, depending on the UI framework, what about giving them the means of simply saying:
LF=Environment.NewLine;
MSG01="...{LF}...";
Or combine things together recursively with:
MSG11 = "{MSG01}{LF}{MSG52b}";
and be done with it!
In other words, we're simply giving them not just a resource file to create -- but a micro-DSL language to work with.
Here's a first pass at what I am thinking could be a better solution...let me know your thoughts on it.
Read the rest of entry »
This is one for the books in HowMyTimeGotWasted… So you’ve built a web application and a Web Setup deployment project, and it’s worked fine. And then it stops working for no clear reason. Error Message is: which doesn’t give you much. Output is: ------ Build started: Project: Corp.Framework.Common, Configuration: Debug Any CPU ------
Corp.Framework.Common -> C:\Workspace.SWS\trunk\SWS\Corp.Framework.Common\bin\Debug\Corp.Framework.Common.dll
------ Build started: Project: SWS. ...
Read the rest of entry »
After defining some precompiler variables as follows: <!-- ex: SomeCompany.SomeDiv.SomeAppName --><?define PRODUCTTARGETNAME = "$(var.ConsoleApplication1.TargetName)"?><!-- ex: http://somecompany.com/products/$(var.PRODUCTTARGETNAME) --><?define PRODUCT_INFO_URL = "http://somecompany.com/products/$(var.PRODUCTTARGETNAME)"?><!-- ex: c:\Workspace\SolutionDir\ProjectDir\SomeCompany.SomeDiv.SomeAppName.exe --><?define PRODUCTTARGETPATH = "$(v ...
Read the rest of entry »