-
-
A new beta of Internet Explorer 7 (Beta 3). Download it here http://www.microsoft.com/windows/ie/downloads/default.mspx.
I also confirm that .Text Admin Tabs works perfectly! Bye bye IE6. More Beta 3 features here: http://www.microsoft.com/windows/ie/downloads/default.mspx.
This month is also started with a talk @ ST Inten about Visual Studio 2005 Express Edition to build .NET Framework 3.0 applications. Slides going to my public Box.net folder soon!
-
-
Introduction to Web Services @ ST Inten - 29 June 2006
Topics covered:
- What is Web Services
- Creating a Web Service
- Consuming a Web Service
Workshop materials will be available soon... See you there!
Update 29/06/06: files are downloadable from my Public Box.net Folder. Look for the link in the right bar.
-
-
There's a difference when defining attribute between C# and Visual Basic.
I was converting the following code snippet, a typical WCF contract definition. (In fact, it was taken from a ChatRoom sample from netfx3.com.)
[ServiceContract(Session = true, CallbackContract = typeof(IChatCallback))]
interface IChat
Logically, the attribute part should be translated into this in VB:
<ServiceContract(Session = true, CallbackContract = GetType(IChatCallback))> Public Interface IChat
Well, it's not. First of all, there is no such thing as assignment operation in parameter area (the above code is constructor call of ServiceContract attribute class. The Intellisense gave away unhelpful cue to do the above conversion. It displays tooltip like:
New([CallbackContract As System.Type], [ConfigurationName As String], ... and so on. Based on the info, I tried giving all of the information it requests by coding it like this:
<ServiceContract(GetType(IchatCallback), , ... and so on. In the end, VS complains about “Too many arguments to 'Public Sub New()'.” Using the Object Explorer, clearly that the definition of the constructor is without parameter. After digging through samples, luckily there's a hint on one of the samples from MSDN. You should use “:=” in place of “=” to do the assignment in VB. So the above C# code can be translated into:
<ServiceContract(Session:=true, CallbackContract:=GetType(IChatCallback))> Public Interface IChat
That line, does the job.
-
-
I've started using Microsoft Office Visio 2007 Beta 2 today. There are several improvements to the application, although it is still using the standard menu bar (no ribbon here). Microsoft has provided the out-of-the-box installation with several new templates. The previously available templates are also graphically revamped.
One of the notable feature is "Drop and Connect Shape" feature. This feature reduces dragging and dropping common to the previous version of Visio. Here's how it works:
- Drag and drop the first shape to the page.
- Hover above the shape, you will notice 4 blue arrows to the top, right, bottom, and left of the shape.
- Hovering above the arrow, you will see tooltip saying something like "Drop and Connect 'name of shape' Shape".
- Try clicking on the arrow, Visio will drag and drop the same shape you dragged earlier to the direction of the arrow you clicked, and added the connection lines automatically.
- What if I wanted to add a different shape? Easy, just select the shape you want to put from the toolbox, and then click the blue arrow to put the selected shape.
There's also a new feature called PivotDiagram, haven't got around it yet, but I think it is some sort of databound shapes. Data can be taken from Excel (or supposedly any OLE DB connection).
-
-
While most of us here still trying to crunch in what's new in .NET Framework 2.0 (things like Generics, etc.) those guys at Redmond already start to develop .NET Framework 3.0.
"What? Did I read .NET Framework 3.0? I thought 2.0 was the last version!“
Well, not anymore. WinFX is renamed to .NET Framework 3.0. It's not exactly fixed yet, since it's just a name change.
About WinFX or .NET Framework 3.0 (as of writing): it's an addition to the .NET Framework 2.0 released last year. All of the features of 2.0 is added with Foundations from Windows Vista (that is, Windows Presentation Foundation, Windows Communication Foundation, Windows Workflow, and Windows CardSpace (formerly InfoCard)). So, you will use 2.0 compiler, using 2.0 language, but have access to Windows Vista Foundation classes.
More information on Soma's and Jason's.
Personally, I prefer naming the whole thing .NET Framework 2.5 or .NET 2.0 FX since it's just built on top of the latter version. Reduces confusion with the next version of C# or VB (3.0).
-
-
Currently, I'm experiencing from what seems like a degradation of quality from the last build I've installed (5308).
My modem does not work 100% perfectly. Every time after a restart, you will need to reinstall the modem driver so that you avoid getting the “no dial tone” message.
My on-board audio chip does this annoying things of not playing any sound at all at one time, and playing perfectly fine at the other times. (haven't really found out what the culprit is)
Both problems does not exist in 5308 build. Are you guys shipping this thing?
P.S.: Another, non-motherboard related problem is with Yahoo! Messenger. Damn this app sucks. From non-functioning visual controls to annoying focus leecher (experienced on win xp). I'm amazed that people still use it. Sigh.
-
-
Please welcome the latest family in the Team System line. Dubbed Visual Studio Team Edition for Database Professional, this product promotes inclusion of database into the application lifecycle management.
From my POV, I think it's just a database source control. Very important when you deal with a lot of tables.
CTP is downloadable after TechEd, which is June 11.
More information http://msdn.microsoft.com/vstudio/teamsystem/products/dbpro/default.aspx.