One of the best JSON libraries just got better. James Newton-King just released version 6.0 release 4 of JSON.NET! It came out on August 4th, but I just came across it. This is not just a bug fix release. Some of the updates include:
- Merge – makes it super simple to merge JSON
- ConstructorInfo properties replaced with functions – simplifies Dependency Injection
- Metadata properties no longer have to be ordered first
- XML document type support!
And more! And to top it off, he gave it a nice performance boost! Nice work!
Last night I purchased the Kindle book Bootstrap 3 by Ryan Flores. It’s a small book and it does not attempt to be a ‘teach me how to do everything’ type of book. It is written to help you do one thing: get up and using Bootstrap quickly. It does that one thing very well.
Ryan’s style of walking you through a few examples, does an excellent job of helping you understand the basics that you have to know and understand in order to use Bootstrap 3 effectively.
The price on Amazon was $2.99 and I finished it in half a day. And that includes chasing down questions that I had while working through the examples!
This is definitely a book you need on your electronic bookshelf!
This is yet another post about WPF. We all know that WinForms is dead or dying, still used but anyone learning development should not spend time on it. WPF was once thought to have had the door slammed shut on it, but like all good technology, it is still alive and improving. We have some great things coming for WPF 4.5 (my favorite is accessing collections on non-UI threads!). Jerry Nixon did a pretty good write up on the primary features coming in WPF 4.5 and can be found here. There is also a pretty good video from Pete Brown on the bottom of that page. Our good friends over at Infragistics also provided some more information and can be located here. Antonio Luevano put together a pretty good PowerPoint that you can download from here. All in all, if we as developers can pick up the new features and run with them, we can help influence/guide/prod/push/coerce/convince Microsoft that this is a good technology that can have a good long life.
Enjoy and Happy Coding!
Sometimes it blows me away to see an error message that is so confusing that I don’t wonder why people get frustrated with new technology. Take for instance this error you might see when building a WPF application. I had a WPF application that I was polishing and happened to add a background to a report page. It took me several minutes to determine what the problem was because, as you can see, the error didn’t really indicate clearly what the problem was.
The root cause was that when I added the Grid.Background, I had not provided a path and the file was in the solution directory, so it looked fine during design but failed when I tried to run the application.
The fix was simple, I put the file on a hosted share and gave a web URL for the image.
I hope that helps someone avoid the headache I had.
** One additional note ** Changing the target framework to 3.5 clarified the error greatly. Kudos to the 3.5 .Net guys. ***
As some of you know the Oracle drivers can be somewhat…..painful to say the least. Oracle still hasn’t gotten the ‘universal’ driver install working consistently, but the x64 driver install does seem much more stable. I played with the XCopy version for just a minute before bailing on that and going with the SETUP version.
However, one thing I would suggest is that if you were running the 32bit version previously, I would strongly suggest you remove the 32bit version. It will just save you loads of confusion and possibly pulling some of your hair out.
Once you install the 64bit, be sure to change all your 32bit projects to 64bit.
When I do a posting, I try to do my research. When I added my last post about WPF seemingly “disappearing” from MSDN, I wasn’t expecting the immediate response about how WPF is going strong. Yes, what I said about the WPF home page on MSDN was true. However, there was some hidden information that I didn’t have.
A friend directed me to the new Introduction to WPF 4.5 page on MSDN. Once I got to that page, I found links to several other great WPF pages on MSDN. It would seem that WPF is not just alive, but it is evolving. If you do some searches, you can actually find some Win 8 development pages showing XAML. You can make your own conjectures just as I have.
As for the WPF docs on MSDN, that would appear that someone over at the MSDN group is not handling that evolution well.
Oh, and even though getting flamed isn’t fun. I’m really happy to get the clarification on WPF (especially from those who would really know). In my opinion, WPF is a big improvement over WinForms and is a significant investment. I know nothing lasts forever (remember VB6 forms and/or C++ MFC forms?) but for now, it seems like my WPF investments are still holding their value.
Subtly and quietly, Microsoft has been removing WPF resources from the MSDN site. If you click on the link that used to take you to the WPF home, you will be directed to the general Visual Studio .Net Framework home.
WinForms has been a thorn in Microsoft’s side for a while and it would appear that they want to remove the WPF thorn as quickly as possible. It’s a shame, really, WPF has some really good qualities.
I can’t really complain though. If you look at something like Java/Swing/AWT/JavaFX, Oracle can’t pull it all together fast enough. Sure the toolsets have really improved, but the base product itself (the libraries) just aren’t up to snuff.
That’s my two cents worth.