VS.NET RC1 is available for download for MSDN members.

Microsoft Journal is back !!!

I wonder if anybody can help. I want to do an HTMLEncode in VC++ with minimal runtime dependencies. A lot of ASP/Site Server/Index Server objects have this - but surely this is a utility function and shouldn't be associated with a server instance ? Does anybody have any code to do this, or know of any library routines - that will probably be installed on the client machine ? TIA JoeW

Thanks for your suggestions guys. I wonder, has anybody had any experience of HTML+TIME - are there any editors that support this ?

A few points, forgive me if I'm mistaken: Where's your code to actually print the character... something like: if (typed >= (short)('A') && typed<=(short)('Z')) { gotoxy(x+i,13); cprintf(typed); } also, your backspace code needs to read something like: if (typed == 8 && i > 0) { gotoxy(x+i-1,13);cprintf(" "); i--; } Where 'x' is your initial starting point.

I personally like VJ++ and think it's a lot more stable than any of the other IDEs that I've used. It depends on what you're after. You must realise that VJ++ does not run the same IDE as VC++ - instead it shares the IDE with Visual Interdev. Best thing is to try some of the other IDEs around (using the trial version), or use the command line.

How about: ".NET is the set of technologies that allows software components to interoperate as services on the Internet, running on any platform, using any language.

Agreed. I think the most important aspect of .NET is that it's a platform and not a Windows technology. You compile your code to MSIL (Intermediate Language) and the software is written CLR (Common Language Runtime). Microsoft's main languages will all have a development mode, where the .NET 'virtual machine' is targetted. In some cases this will be the only mode. For the first time since MS's fallout with IBM they're pushing developers onto a different platform other than Windows. What will the Net result be ? Applications being more connected, richer Web Applications targetting .NET on the client and downgrading seamlessly for incompatible platforms. Potentially the end of clumsy HTML browser applications trying to emulate their richer Windows equivalents. More stable applications, no leakage - less GPFs etc.

I assume that you mean Office 10, Office.NET is the next version after the next... if you see what I mean. As Word and the other Office Apps don't use the standard Windows controls for text editing, it's quite possible that we won't see new Windows messages for getting multiple selections. That said, with the new policy on service pack upgrades to the OS instead of side-effect upgrades through application instalations, I bet that a requirement for the new version of Office will be Service Pack X.

.NET Web Services uses SOAP, which is an Open Spec used on any platform - including Java. .Net is a lot more, it's also a brand new platform - much like the JVM. I'd say that this is the main thrust - and the main change that developers are going to have to deal with. It effectively signals the end of MFC and ATL as evolving libraries. The Web Service aspect is more marketing than anything else. Your point about who will pay for the services is interesting. It's has been pointed out that the current advertising model will no longer work for these services. Think about a search engine that publishes a Web Service, how do they get their money - what's their cost structure? I wouldn't say this is going to be a problem for .NET - more a problem for evolving the cost structure of the Internet itself. The only solution that I can think of is to pass the revenue down from the main client site down to the services that they use - this means that these services will not be free.

I think most people accept that C# and most of the .NET runtime technology is based on Visual J++ and it's JVM. Who would have thought that the future of the Windows platform would be born out of what Microsoft use to call 'Jakarta' ?!

In all honesty, I think the outcome will be become a irrelevent. We'll end up with the JVM stubs onto the .NET environment and vice-versa. Competing on implementations, rahter than specifications. "the eternal optimist" Joe

Clearcase was good, for large projects but its servers use a case sensitive filing system. This is a problem in VB/VC where the IDE tends to change the case of the files based on the entry in the project file. SourceSafe is nice and simple, but not so good for branching and large teams. One thing that I noticed about .NET... what's happening to Source Safe. At one stage there was a lot of talk about building version management into the Filing system??