Robert McLaws's company Interscape (which I presume we are all familiar with ;) just released a VS.net addon, called Deadbolt.net that simplifies assembly signing. I think that addon is a great idea and probably will help people who otherwise would not sign their assemblys. But should those people be publishing signed assemblys ? Should people who are not that familiar with strong names and .net security be publishing assemblys that can by registered with the GAC ? Might that be the reason MS skipped the "sign assembly" menu item in their release ?
Verisign makes it pretty hard for people to buy their certificates, that is so you can trust the sites verisign signs. Because you know SmallTimeCrocksLookingForQuickCash.com will not get certified by VeriSign. The same I think about signed assemblys, sure everyone with sn.exe can sign and create strongly named assemblys, but doing so requires basic understanding in .net security, therefore making the signature more trustworthy.
Anybody read the Design Patterns for Scalable Microsoft .NET Applications ebook from sundblad&sundblad. It's mentioned in Designing Scalable .NET Applications from Apress which I liked a lot.
I'm quite insecure about buying books which have no visible reviews ala amazon.
Any book advanced .net architecture book recommendations you guys have, or any advanced .net books for that matter ? What are you guys reading at the moment ?
I just saw Microsoft has created a Standard Version of it's CMS product, set at 6,999$ per CPU.
This might cause quite a blow for us ISV that are developing our own CMS systems, priced in the same range as MSCMS Standard.
"Pricing for CMS SE will start at $6,999 ERP per CPU. It will be limited to 15 content contributors and also will offer a Microsoft Content Management Server 2002 Connector for SharePoint Technologies."
With asp.net we got the feature of being able to store session state out of the worker process, so if the asp.net application restarts (a common thing, touching the /bin or web.config file causes a restart) the session state is still there.
But why are we not able to store our cached stuff out of process also and in a aspnet_cache provider service running on our www servers ?
Why not implement a provider model for the cache, so that we can play around with our .config and /bin and cause endless .aspx recompiles without loosing our precious cache ?
I hope I will be able to find this in Whidbey , although I have not seen a word about it (note to self: Finish those PDC slides !)
UPDATE:
Just as I pushed POST I remembered the Caching Application Block for .NET which seems to provide this feature.
"Data can be cached in several formats, including a Microsoft SQL Server™ 2000 database, a memory-mapped file, or a singleton object. The Caching Application Block also includes example classes for caching, scavenging, expiration, and data protection. "
Still, I wish this was a provider for the default asp.net caching API
Some new great things in there in release 0.29, but the thing the grabbed my attention was : ASP.NET: Feature complete
Check it out here