|
Sponsored Links
Resources
.NET Research Library
Get .NET related white papers, case studies and webcasts
|
|
Message #138164
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
 |
Short IDs are stable, aliases are not
I should point out that URLs like http://msdn2.microsoft.com/library/System.IO.Compression.GZipStream are specifically *not* designed to be stable "now and forevermore". That feature is reserved for URLs of the form
http://msdn2.microsoft.com/library/a1b2c3d4
(the short ID format). The reason for this is obvious: as new versions of the framework ship, there will be multiple documents that correspond to "System.IO.Compression.GZipStream" - the older ones and the new one. An alias will (probably) point to the latest one, but the short ID will remain stable against a particular version "now and forevermore".
|
|
|
Message #138210
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
firefox
They have a long way to go for firefox support, the page looks pretty bad. I'm sure they will get it better before release.
|
|
|
Message #138223
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
firefox
They have a long way to go for firefox support, the page looks pretty bad. I'm sure they will get it better before release. I would strongly suggest posting concrete problems you're having with using Firefox; while I won't speak for the devs (Tim and Craig and the others), I know that when working on web projects, the more concrete problems I know about for each exact browser release, the better, since it's often hard to repro problems on each and every single browser ever released. :-/
|
|
|
Message #138228
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
firefox
it's often hard to repro problems on each and every single browser ever released. :-/ Firefox isn't 'each and every single browser', it's the most or second most important browser in the market right now (mozilla uses the same engine).
|
|
|
Message #138236
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
firefox
Ok, problems: this are when comparing to IE, which is what I'm guessing they are testing against first.
+ "GZipStream Class" header bar is going full width instead of terminating against the "Page Options" box.
+ All code(grey area and objects above) are entirely to small to even read. The rest of the text looks appropiately sized.
+ Side menu, boxes created when hovering, overlap text above and below.
+ The footer and header bars have to much "height", creating more gap than intended. Also the color gradient doesn't work(same as microsoft.com home page).
That last one has always confused me. I think MS is using dhtml but I don't know if it's specific to IE or ff doesn't support or what is going on there. I know IE does some CSS3 stuff that ff doesn't support(and I wish they did, see CSS3 behavior module).
|
|
|
Message #138252
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
firefox
That's good feedback that the folks at MSDN will be able to use to correct these problems. Still, I wanted to point out just a few things.
- msdn2 is a beta version, so a few glitches is perfectly understandable and I'm sure the docs will be perfectly readable in the final version
- CSS3 behaviors standardize an idea that's been present in IE since version 5, IIRC
- Look at the Mozilla DOM documentation (which is not beta) with IE. It's not pretty.
|
|
|
Message #138342
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
firefox
Firefox isn't 'each and every single browser', it's the most or second most important browser in the market right now (mozilla uses the same engine). It is however a browser that is in Beta. Who's to say that a change made to ensure Firefox compatability won't have to be made again later, when the product is shipped? If it were my site, I'd wait for an actual release before making any changes for compatability.
Which brings up another point. If Firefox does in fact gain popularity, are we looking at another browser war? Or maybe instead of trying to write HTML that will be interpreted by either browser, we could just all move to smart client deployed .NET applications and give up on antiquated HTML and Javascript. That would be my vote.
|
|
|
Message #138353
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
re: firefox
Firefox isn't 'each and every single browser', it's the most or second most important browser in the market right now (mozilla uses the same engine). It is however a browser that is in Beta. Who's to say that a change made to ensure Firefox compatability won't have to be made again later, when the product is shipped? If it were my site, I'd wait for an actual release before making any changes for compatability.
What I'd personally advocate, is that designers develop their pages according to the present day w3c standards that the majority of browsers have implemented. It's honestly the easiest way to ensure your pages will be functional across different browsers. You generally will have to make a few tweaks to support IE, but they're mostly well documented bugs with easy solutions. The new MSDN site would be very easy to redesign in a standards based way, the will just has to be there.
|
|
|
Message #138361
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
I guess I should look at the page first
The new MSDN site would be very easy to redesign in a standards based way, the will just has to be there. After looking at the page, it actually appears that they've done a pretty damn good job of writing to standards. The bugs with the table of contents in Firefox are in the CSS... On first glance, it looks like Firefox is actually handling the links exactly the way it should.
I might do a few things differently, like having the ToC and main menu links within li elements instead of divs, but otherwise they're well down the path to standards-based goodness. Nice job MS.
|
|
|
Message #138450
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
I guess I should look at the page first
This brings up a very good point. Should Microsoft consider creating a version of MSDN that is deployed as a smart client? Imagine the features and functionality it could provide. You could click a button and put sample code into Visual Studio, or see running Windows Forms examples.
Next week TheServerSide.NET is going to sponsor another debate on using Rich Clients vs. Browser Interfaces. It will be interesting to see where the community's loyalties lay.
|
|
|
| |
|
| New content on TheServerSide.NETNew content on TheServerSide.NETNew content on TheServerSide.NET |
|
|
Language "mashups" will become more prominent, and developers will become polyglots, one programmer suggests.
SearchWinDevelopment.com offers an introduction to the language, performance, testing and data management improvements in VS 2008.
VBCode.com code snippets cover all aspects of application development, from data binding to security to the user interface.
Get up to date on XAML best practices with a variety of articles, tutorials and webcasts. [SearchWinDevelopment.com]
One team's experience with the VSTS DB edition suggests that it can improve workflow for dev teams. It also enhanced Agile efforts.
(June 24, Article)
Microsoft has begun to include DSL tools in the VSTS kit. A new book by Steve Cook and other VSTS team members helps set the stage.
(June 24, Article)
Cartoon: Be it ever so humble there is no place like your home after you get a Microsoft Home Server .
(June 18, Cartoon)
Microsoft's Thom Robbins says new technology to highlight in NET 3.5 includes AJAX, LINQ for both C# and VB, as well as tooling enhancements intended to ease the task of building WPF, WF and WCF apps.
(June 29, Podcast)
Venkat Subramaniam discusses AJAX bottlenecks, the tenets of Agile development and more. He spoke at the Ajax Experience.
(June 25, Tech Talk)
In the second of a two-part series, Michele Leroux Bustamente discusses design decisions related to the claims-based security model. Read the story and walk through the process for creating a set of claims-based utilities to encapsulate claims authorization at the service tier.
(May 24, Article)
Understanding why the Entity Framework exists and learning where it can fit into your projects can get you prepared for the eventual release early next year.
(May 10, Article)
Resource: This learning guide gives you quick access to useful links on Windows Communication Foundation security information.
(April 24, Article)
TSS.NET's Jack Vaughan spoke recently spoke with Microsoft's Brad Abrams to find out what he is seeing in the field and what the chefs in Redmond are cooking. Along the way he discusses patterns of AJAX frameworks.
(April 11, Article)
In a two-part series, Michele Leroux Bustamente explains how claims-based security is supported by WCF, and how you can implement a claims-based security model for your services.
(March 29, Article)
Windows Workflow Foundation is a new technology that many developers will need to get their heads around. In a brief excerpt adapted from Programming Windows Workflow Foundation: Practical WF Techniques and Examples using XAML and C#, K.Scott Allen considers aspects of workflow definition.
(March 22, Chapter Excerpt)
|
|
