March 2004 - Posts
News from Repeou:
The country Repeou threatens Microsoft to pay a fine as much as 10 percent of its global annual sales for monopoly defenses. The software giant is abusing its monopoly power by bundling several applications such as the Calculator and Paint with Windows.
The process against Microsoft was started by the company named Nisbum. Nisbum developed a great calculator but doesn't see a chance to sell this great product to the masses as long as Microsoft bundles the Calculator with Windows.
According to Repeou, Microsoft must offer at least two separate versions of Windows, one version without the Calculator.
Repeou is giving Microsoft a last opportunity to comment before the case is concluded.
What are the boundaries of an operating system? The boundaries of operating systems shouldn't be defined by governments, and they shouldn't be defined by competitors.
Update (too many readers take this serious):
This story is a joke - related to the EU case against Microsoft. There is no country with the name Repeou, and I don't know a company named Nisbum. However, you can rearrange the letters of the country and company, and you will get some real values here. BTW, two companies ;-)
Just a few chapters left :-)
Chapter 13 is about deployment and configuration of Enterprise Services applications.
Dynamic registration of serviced components is only useful during development (and here this is very useful). On the production system a real installation of the serviced components is needed.
This chapter covers all the options of the regsvcs utility and creating Windows installer packages. I'm also showing how the COM+ Admin components can be used to configure serviced components. Not all options are available by using .NET attributes.
Channel 9 has a page update: channel 9 coming soon..
Roy points out that there's already more information out there. I've checked the blogs and found this:
Today I had a meeting about Channel 9. Cool things are coming :-)
At the moment I cannot tell you more about it ;-)
Just check the link from time to time.
Chapter 12 covers many aspects of security with distributed applications. Because serviced components do not stand alone in a distributed solution, the chapter covers security with
- SQL Server
- Internet Information Server
- ASP.NET Web Applications
- ASP.NET Web Services
Of course the biggest part in this chapter is security with Enterprise Services: role-based security, identity configuration, impersonation and delegation, security with .NET Remoting.
On Tuesday Mario Szpuszta has given a great presentation about SQL Server 2005: SQL Server Programmability & CLR Integration for the SQL Server Usergroup Austria.
Some highlights from Mario's presentation:
Hosting of the .NET Runtime
SQL Server hosts the .NET runtime, but of course SQL Server has higher requirements than other hosts. The runtime runs in the same process as the SQL Server (that's different from similar technologies from other vendors). This also means bigger security requirements. Both the .NET runtime hosting interfaces as well as the SQL Server had been changed to fulfill these requirements. SQL server has control over threads, memory...
SQL Server has 3 groups to control security for assemblies:
- Safe: only defined FX may be used
- External access: network and file system access is allowed
- Unsafe: this is unrestricted
SQL Server uses 1 application domain for every database - compare this to the ASP.NET runtime that uses 1 application domain with every web site (IIS 6 also has application pools - different processes).
.NET Code and T-SQL
Mario demonstrated creating assemblies for SQL Server. Writing C# code in the serer is a great feature! This doesn't mean T-SQL shouldn't be used anymore. T-SQL is better (and easier) for relational access, while .NET code helps doing complex statements.
Why put logic in the database - a weblog by Mario.
User defined types can be defined as ordinary .NET classes. However, there are strict requirements: onversion from/to string; optional nullability by implementing the interface INullable, no inheritance. UDTs can also be only normal columns (no indexing). Check constraint is possible.
It is possible to define user defined aggregates for UDTs. Aggregates are defined by .NET classes with four methods: Init, Accumulate, Merge, and Terminate and some properties.
A issue with UDTs is that if a new version should be used, all dependencies must be recreated (tables). This issue may change with the release.
Mario started a discussion about .NET UDTs in his weblog.
Current plans for dates:
Beta 2 - Summer 2004
Beta 3 - Q4 2004
RTM - 2005
More information about the beta plans in Tom Rizzo's blog The Road to Yukon.
Mario has read the book Presenting to Win - The Art of Telling Your Story and adapted all his presentations with information from this book. I'm just doing the same. :-)
Today Hannes Preishuber (INETA Speaker) had a great presentation about ASP.NET Web Application Security for the .NET User Group Austria: a very interesting presentation covering exploits from web sites.
We had a really high attendee count - this presentation interested a lot of developers: a good way to the right direction regarding security :-)
Still a lot needs to be done that every developer is aware of security issues.
Hannes will repeat this presentation in Graz and on a tour through Germany.
INETA is going to be running the Birds of a Feather (BOF) again this year.
More information at Bill Evjen's Blog!
Chapter 11 is about Loosely Coupled Events (LCE). First I'm comparing LCE with COM Events (Connection Points), and .NET Events, then these topics are covered:
- Architecture of LCE
- Programming LCE
- Using LCE across the Network
- LCE and Queued Components
More Posts Next page »