eWeek writes about the Digipede Framework SDK
Darryl Taft at eWeek posted an article yesterday on one of the things we’ll be showing next week at PDC05:
Digipede to Release SDK for Windows Grids
Have I said that I’m looking forward to the PDC?
rwandering.net
The blogged wandering of Robert W. AndersonAuthor Archive
Run Plazes while at PDC05
I have been checking out Plazes. If you haven’t tried it out yet, it is a way to share your location with others where location is defined by the network you are running on.
Kind of cool, but not too useful when sitting at home or in the office. I’m looking forward to trying it out at PDC05 to see how many people (and geeks like me) come up on the Plazes radar.
Maybe I’ll “see” you there.
Scoble says we’ll be amazed at PDC
Today on channel 9, Robert Scoble asked for guesses about what will be announced at PDC next week (because no one seems to have a clue). Then he blogs that PDC05 will prove that Microsoft is definitely not “roadkill.”
I certainly didn’t think Microsoft is roadkill — but I’m glad I’ll be there to find out first-hand.
See Ye old “guess what MSFT is gonna show at the PDC
and Steve says Microsoft is roadkill (and a few other things), respectively.
COM APIs for .NET Libraries
Recently I added a COM API to the Digipede Framework API – developing a good, maintainable COM API was critical. The “easy” Microsoft .NET COM interop works pretty well, but it defaults too many things for those of us building public libraries.
If your public library needs to support COM, there are several steps you will want to take to make your COM API easier to maintain and to allow your library to behave (or appear) as COM clients expect.
I am thinking of writing an article (or a series of blog entries) on the steps I took designing our COM API. While some material exists out there on this (most of it pure reference), none of it brings it all together, soup to nuts.
My quick outline for the article:
- Introduction
- Limitations of COM interfaces
- Overriding the class interface
- Eventing interfaces
- Building your Type Library
- Embedding your Type Library
- Enabling Registration-Free COM
- Building a COM API Reference w/NDoc
Every section will include examples.
I guess my only question is: do I blog it or write an article for one of the many .NET related sites? If I write an article, which site should I submit it to?
Designing .NET Class Libraries
I was talking to a friend of mine the other day about Microsoft and why I choose to develop software for their OS versus some other platform. I won’t post all of that discussion here, but one point I made to him was that Microsoft provides excellent resources to their developer community.
I don’t think I really need to further make that point here (anyone interested in reading my blog probably buys into this view already); however, it did remind me of a series on API design that I downloaded from MSDN earlier in the year. Designing .NET Class Libraries provides good information for all .NET developers, regardless of whether you are designing public libraries or not.
Designing .NET Class Libraries
It is worth the time investment.
Going to PDC05
My company, Digipede Technologies, will be promoting our new SDK at PDC05 next week. At the same time we will be announcing and giving away free licenses to the Digipede Network Developer Edition.
I am looking forward to the trip. In my past companies, the clientele was often not technical outside of their particular vertical experience. As software developers are one of the primary targets for the Digipede Network, I’m happy that our customers and prospective customers are highly technical. This makes the customer meetings much more interesting for me and productive on many different levels.
Basically: We’ll get to talk to lots of smart people about what we are doing. And that is always fun.
What is R Wandering?
This blog will track my thoughts on software, process, tools, and technologies. I will also use it as a place to post approaches and solutions to technical problems I come across. I have a bit of a backlog of these that I plan to write up over the next month (e.g., some nant and ccnet stuff, developing COM interfaces and documentation for .NET, some Preemptive posts . . . ).
I have been developing software since high school and basically full time since I was a Junior at Cal. I finished there 15 years ago and have since helped build a couple of companies as the software technology lead. While my primary responsibility is generally planning, designing, and building software product I have also been responsible for or directly involved in every aspect of the business. I’ve been on company boards, managed human resources, hired and fired, performed technical selling and evangelism, worked through various due-diligence processes, sold a company, and more. Aside from developing software, one of my favorite things to do is to discuss business issues with fellow entrepreneurs.
My company, Digipede Technologies (www.digipede.net), sells the Digipede Network, a Windows-based distributed computing product built upon Microsoft .NET.
I became interested in distributed computing while at Energy Interactive (www.energyinteractive.com). Among other products we had an energy billing solution designed for billing the most complex commercial and industrial customer for energy providers. Billing was a long running process and we needed to come up with a way to shorten the total run time for a billing cycle. When scaling up was no longer an option, we did the next logical thing: we scaled out. To do this, we ended up rolling our own solution using DCOM, but, we felt that there had to be a better way. That is one of the motivations for the Digipede Network –a packaged solution with the tools to make it easy to grid-enable applications.
In terms of development technologies, I’ve spent most of my time working with Microsoft tools and technologies. I first started with Windows 2.0 and have, of course, worked on all of the Microsoft platforms since. I have worked with C++, VB, MFC, COM/DCOM, ATL, everything from ODBC to ADO.NET, Java, MSMQ, SQL Server, C#, ASP.NET, and more. Now, I am fully a .NET and WinFx developer.
In addition to my work I also manage a couple of FreeBSD servers for hosting email and Web sites.
And none of that explicitly defines R Wandering.
About me
Main feed
Email subscriptions