Skip to main content

Even MSDN Library doesn't know VFP isn't in .Net!



Get a load of the picture here. It's clearly VFP 9 help - there's nothing that would say anything else except for that little blurb on the side:

This page is specific to
Microsoft Visual Studio 2005/.NET Framework 2.0

Other versions are also available for the following:

# Microsoft Visual Studio Codename Orcas


The direct link is here. However, if you go down further on the page, you'll see that Microsoft is trying to encourage community redesign of the MSDN library. You can add community content about any particular element of the VFP help file.

Definitely helpful - makes me wish that the Task Pane or VFP itself had an option to push developers directly to the MSDN online help, instead of the regular CHM file.

That did make my Friday though.

Comments

Cesar Chalom said…
Hi Andrew,
MSDN Community Content is for sure a big deal... but unfortunately I haven't seen things published there.

As the GdiPlusX library is compatible with .NET "System.Drawing" namespace, I added some contents in some links. But nobody seems to care with them. I even blogged about it, but got ZERO feedback, so I've quit putting codes there.

http://weblogs.foxite.com/cesarchalom/archive/2007/02/05/3238.aspx

Here are the links with the VFP code that I posted:
http://msdn2.microsoft.com/en-us/library/system.drawing.fontfamily.getfamilies.aspx
http://msdn2.microsoft.com/en-us/library/5wx970a5.aspx
http://msdn2.microsoft.com/en-us/library/16k3da3w.aspx
http://msdn2.microsoft.com/en-us/library/System.Drawing.Drawing2D.GraphicsPath.Clone%28vs.80%29.aspx
http://msdn2.microsoft.com/en-us/library/fz2042a8(VS.80).aspx
http://msdn2.microsoft.com/en-us/library/865tf5y6(VS.80).aspx
Eric said…
Just because we don't comment doesn't mean we don't care! There are myriad reasons why we may not comment, but I for one really really appreciate it when someone takes the time to share good code samples, or blog about interesting things.

Popular posts from this blog

FoxInCloud Stats

FoxInCloud sent this link a while back about their statistics regarding visits to their site:

http://foxincloud.com/blog/2017/12/27/VFP-community-lessons-from-foxincloud-site.html



What's interesting here is the breakdown of people. Yes, I think it's understandable that the Fox community is getting older.

Another factor is the growth of the mobile and web environments taking over development. These environments really do push people towards the newer non-SQL or free SQL/hosted environments but more towards hosted storage options like Amazon and Google. A tool like FoxInCloud that helps MOVE existing applications to the cloud inherently competes with those environments.

But FoxInCloud also allows developers to extend their application further by giving them a starting point using Javascript and the basic CSS (such as Bootstrap). If you're not rebuilding your application from scratch, it's certainly a great step forward.

Well, that explains CodePlex...

In a move that will be sure to anger open source (or rather anti-paid software, anti-Microsoft open source)  zealots, Microsoft is planning to buy GitHub.

A year ago, I mused about why Microsoft would shut down CodePlex and how the world needs competing source code repositories to be strong. I'm not the only one per this Slashdot article :
"...people have warned about GitHub becoming as large as it did as problematic because it concentrates too much of the power to make or break the open source world in a single entity, moreso because there were valid questions about GitHubs financial viability...." - Jacques Mattheij

I will be interested in seeing this play out - whether developers jump ship or not. Have all the efforts Microsoft has made in pushing towards open source be seen as genuine or will all the zealots jump ship or maybe even attack?

Microsoft's comment about why they shut down CodePlex referred to how spammers were using CodePlex. Well, GitHub has its own …

The World of Updates Today

I just received an update for Office 365. It certainly includes some cool features - including starting in one environment and picking it up in another environment. In recent years, I've certainly enjoined the use of Continuity on a Mac and in fact, I feel spoiled being able to start a message in one environment (even Google) and then finish it off on another.  This has become some pervasive when we were reviewing our most recent backlog at a client site, a similar feature was added to the current workload.

But with web applications, the trend is to reduce the amount of software on a client machine. I used to have automatic backup for all of my machines (thanks Carbonite!) but these days, many of my machines don't need anything beyond the core OS and some basic applications. Certainly that's the feeling with Chromebooks and even the lightweight aspect of many iOS apps. The functionality is mostly in the cloud.

When you upgrade your system, you expect it to a big update. So…