The WORLD HAS VOTED !

CodeProject.com is one of the most respected sites in current affairs of programming. Below is a poll made by them. The comments are made by me:

Source: http://www.codeproject.com/script/Surveys/View.aspx?srvid=1722&srvsucc=Voted

I'm also a Microsoft Certified Professional in Visual Basic: by Kevin Matney

Yes, I have masters degree in Engineering, but I'm also a Microsoft Certified Professional in Visual Basic, although I received my professional certificate about 6 years after my Master's degree. So I know how to program, and know what I'm doing, and know what my code does, I have software running on multi-million dollar equipment in the worlds most advanced semiconductor fabs. These are mission critical programs, and they are written in VB6 (mostly). I learned the hard way that if you push VB6 too hard, you are asking for trouble, and I had to remove some hardcore API calls I was using. I was only pushing VB6, since it hadn't been updated in so long. So I backed off, and now just live within the limitations of VB6.

VB6 catered to a certain type of programmer, we we took to it like a duck to water. The language just feels natural. You have some of that in VB.Net, but too many other aspects get in the way. I have forced myself to do most (but not all) new programming with VB.Net, and it's been about 2 years, so I'm reasonably proficient. But it still feels like pulling teeth at times - the love just isn't there. If I need to knock out a quick prototype App, I still use VB6, and will do so for many years to come. I tested all my VB6 Apps in Windows 10 and everything works great. So I'm good at least another 10 years.

People forced VB6 limitations and created bunch of hack API stuff, subclassing etc: a comment by Anonymous

People forced VB6 limitations and created bunch of hack API stuff, subclassing etc. There were many 3rd party vendors, who tried to do a buck. It soon became an uncontrollable monster and needed to be put down for many other reasons, mostly it could not really allowed to be expanded and was lacking many important features like multithreading etc. VB6 couldn't be changed easily and to change it you needed to do it from the bottom up. So Microsoft did chose the bottom-up approach and created .NET. This new platform had all the goodies that VB6 didn't have and never could have (because of it's inefficient general design philosophy). That's the reason why pro-coders are now quite happy with .NET today. 
However there is still good news for hobbyist coders, who used VB6 (and still continuing to do so). There is VBA and VB script. VB6 coders can switch to those as they are familiar with the syntax. Besides, there are other languages around like python, which is easy to pick up for non-pro coders. 
Microsoft did the very right think to put VB6 asleep as it was really hopeless, however provided all the help to interop from VB6 to .NET. That's the best that they could honestly do and I don't blame them. 
I suggest that you try .NET, which is getting better each year. (check out NET 2015). However as you are saying that you are a non pro-coder, I would suggest that you use VB6 as it is, because MS support OS support will be there until 2024. But if you need to develop yourself then you should learn .NET, because it is one of the most comprehensive frameworks around for real programmers. Thank you.

Microsoft "evangelists" present the news stuffs as good !: a comment by Michelle

I guess should be the time to seriously think about to abandon Microsoft and their moods. I would remember that EACH SINGLE time they release a new technology, they present and SELL IT as the absolute and definitive good solution for ever. While, in the meantime, they constantly show all the weak point of the past technology like if was made from somebody else!
I've partecipated to hundreds of workshop from Microsoft and their "evangelist" and ALWAYS they present the news stuffs as good, past stuffs with absolutely BAD even if THEY MADE IT. This happened with RDO and then, after a little while ADO was suddendly the new way to god... Also with IIS happened the same. And now it happen with the SDKs...For who is taking the time to read this post, please consider that from .Net 1.0 to .Net 4, ALWAYS a "porting" was needed! Even if you used .Net... but with the new wrong version! At Microsoft seems they do not care AT ALL about developers.

They seems not to understand that all the above "moods" COST MONEY other than time! Bigger the company bigger the costs. Not all the software company around the world have the resources Microsoft have! I hope those are only "moods", otherwise that means at Microsoft they do not know what they are doing! At moment, seems that developers are binded with their operating system and if you want to produce YOUR software, you MUST agree with their politics. Take it or leave it. If you don't agree, you just loose all what you did till that moment! I perfectly understand that the world need to be innovated, but then two considerations came to my mind:

1) I wish to be FREE to decide if I NEED to innovate myself or forced to do it, paying otherwise the penalty to loose my customers or job.
2) If innovation is in terms of software "theology", structure, OOP etc. and the porting from "the past old bad stuffs and habits" is the "new" .Net way of light, please consider that JAVA it's like is .Net NOW, but just years and years ago! So if we want to talk about innovation, then it is Microsoft that is LATE about 10 years, not WE as developers. WE JUST BELIEVED TO THEIR ABILITY to provide a working environment to build software. And Visual Basic 6 IT IS EXACTLY THAT. So, if we are talking about "innovation" seems then that all the developers that trusted on Microsoft's solutions have really used very OLD stuffs, not competitive since the beginning. So, how many of you still believe to continue trusting in Microsoft?

How long this "new and good" .Net technology will remain the same, until the new "porting", in the name of the "innovation"? We have to still trust about the forecast for the support of this .Net product? What about the mandatory switching to Windows 8 if you want to INVEST into the new latest versione of .Net? How many of your customers will feel comfortable to mandatory switch to Win8 only because you started to use the latest .Net framework? Personally, because of the amount of the products and related code I've done in these years I CANNOT AFFORD to "port" it to .Net. Too much complicated. Dot Net is good for "complex" stuffs to do with VB6, but incredibly slow and difficult for basic everydays stuffs. Not to mention the protection of the intellectual property, that with .Net it is simply impossible to really protect. Well.. there are "obfuscators"... good to stop just my grand mother...

That said, if a new Linux Basic SDK appear on the market, I'll for sure reccomend it to ALL OF MY customers, suggesting to switch to Linux. Probably I'll do the switching for free then! Incredibly less cost, more performance, more stability, less problems system-wide. If a new "Linux Basic" that REALLY WORKS will be sold for Linux, I'll go to buy it. 100%. So, who is able to do a compiler, should take this opportunity that Microsoft left open! Whoever will make a Linux Basic, have a market of thousands and thousands of developers, READY TO GO. Those developer, like me, are simply tired to be kept by the neck from Microsoft. We do not switch to other systems simply because there are no good alternatives, or good economic alternatives.
Yet. 

Well... if I'm FORCED to INVEST my time and MONEY somewhere else, there is JAVA, that prooved to be made from who have clear idea in mind about software industry and how to respect who kept the company grow. Do you think that Microsoft could sell so many licenses of Windows and Office, if there was not so many developers around the world?

I respect what Mr. Paul Yuknewicz said. Technically speacking, his points are honestly good points, but economically speacking, and in the way Microsoft usually put decisions, it is totally unacceptable. Refactor VB6 is difficult?!!? This maybe means that doing the .Net was easier?

We have no way to force Microsoft having a "GOOD SENSE OF PRACTICE" other than go away and leave them alone.
So, this is a WORLDWIDE CALL to any developers that are able to make a SDK that have the same ability of VB6, but opened to all the suggestions made in this forum, actualize it, make it for mobile applications too, if possible and with the obvious constraints.
BUT running onto a serious platform: LINUX.
That one will be then a "porting" that could make some sense to do... and not blindly still follow the Microsoft "evangelists" (I'm not kidding. They call like that, by themself, at least here in Italy...).

Kind regards.

Hi, I am one of the censored !

Hi, I am Marius Orion (one of the censored). Your comments will not be censured, I will publish them on my blog, here: http://vb6awards.blogspot.com/

Hundreds of VB6 developers complain that their comments do not appear here: http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/3440221-bring-back-classic-visual-basic-an-improved-versi

Dot not is a junk platform for junk apps: a comment by Anonymous

Dot not is a junk platform for junk apps... hardly anyone uses it. Some do, and some love it. I notice a ***** towards putting vb6 in a past tense, and .net as some 'future'. But to go that route makes Java or Python or any number of other platforms just as good. Why would I choose your next platform, what happens when you dump that one... same argument again... no thanks. And if support stops in 2014 and windows 8.1 then so does my upgrade path... (Think it actually works in windows 10 too). You make big claims for .net, but it never has delivered on them. It's over bearing, over engineered, long winded and designed for a corporate developer, which is great... for them. BUT you've cut loose an awful lot of other developers, the majority in the process. You keep talking about the needs of the developers, whilst ignoring an awful lot of them. I had the displeasure of working with .net to maintain and application for a couple of years, and whilst the GUI design tools where very nice indeed, the language was just plain bad.. long winded and I felt OTT for a small developer of tools like myself. Let me ask you this... there where courses for programming VB6 at the local collage.. no longer.. nobody wanted to learn .net... IT ISN'T FUN... People wan't something approachable.. the .net suites are not. I also note the popularity of Python for teaching programming now.. and can't help feeling that it's because Microsoft has lost sight of a massive portion of it's users. Take care they don't all lose site of MS. If I end up learning something that runs cross platform why would I stick with you guys.. you've already proven you have no idea what people want in a desktop OS and now have confirmed you have no idea what people need to learn programming. I'm really sorry if this sounds offensive BTW, it's not supposed to. I see 10K signings for a development tool as old as this.. name me anything else from back then that people want... no I can't think of anything either.. does that not compute?

VB6 will out-last that entire .NET generation of tools: a comment by Anonymous

.net is just plain awful. Slow, buggy, incompatible tripe. The code isn't even very readable. I know, I've had to use it professionally, however given the choice, to start a new project in ever tighter timescales, VB6 is the ONLY option. Period. I'll be honest, I don't need a new version, just keep it running in your new OS's MS, that's all I need to hear. However, if it does ever die it would actually be less trouble for me to just move to a new platform completely, as other have suggested, so it would be just one more nail in the coffin for Windows generally. If I wasn't a programmer (ok .net peeps, I'm not a programmer in your book), I think it would be quite perverse for a company to ignore a product that is obviously as popular as VB6, even today a top 10 ranking development tool. And one which only exists on Windows. Bearing in mind the ebbing away of Windows fans as it is, can they really throw the baby out with the bath water? Nobody like to admit their wrong, but they should really take their heads out of their ***sses occasionally and see what their own community actually want. By all means, keep developing .net, if that makes you feel any better, but I think most VB6 developers will have already trodden that path and decided it's not for them. I don't think any new version based on the .net model will ever change that, even if people bothered to try it out again (I think I tried out all of them, up to VS 2010 (?)), it didn't get better, fancier, definitely, more complex, absolutely, more powerful, depends on what you think power is (as it's generally slower each rendition), a joy to program in, not at all, anything like VB6, no - it's a totally different language. In another post somewhere, the point was made that .net is the future, but I think VB6 will out-last that entire generation of tools, because it's 'better' for what we, in the real world, need to do. Would it be nice to have an updated, supported and entirely code compatible version of VB6, absolutely. Would it be successful, more than I think even MS could imagine. Will they ever do it, absolutely not. Why? I haven't a clue, it defies logic. Perhaps, like a small child, they just can't admit they where wrong and have become totally absorbed with trying to prove their right. But, as we all seem to know, they did get it very very wrong.

A comment by SuperDre

Standards are just what you use yourself, .NET itself doesn't have any real standards just like VB6 didn't have.. As I've said before, bad code is all down to the developer, and with that, bad code is also very much in the eye of the beholder.. VB6 doesn't stand in your way to use actual development standards, but some people are just too lazy to actually use them, those are the same people who won't use any real standards when they develop in .NET..

Yes, for some stuff you need to 'hack' your way around it, but that's exactly the same with .NET, I've had to 'hack' my way around certain stuff because the .NET framework (at that time) didn't support what I needed or did it in a very unlogical way.. Yes it's nice you can extend you classes and add a lot of attributes, but to me, using those things it's just another fancier way of 'hacking your way around stuff'.. I've sweared a lot at for instance having to use standard .NET components because they just didn't do what they were supposed to do, yeah, unless you are a dummy developer who doesn't actually use it, exactly how you describe VB6 developers (as in NON professional developers)..

And what is exactly spagheti-code, because when I look at a lot of .NET code, to me it also looks a lot like the VB6 code we use (I specifically say 'we use' as I have no real clue to how others work with it)..

Also with .NET you have the problem of having to update your code if you want to use the latest additions, and not all companies have the money to keep updating to the latest version of Visual Studio, or the full version so they can use stuff like the complete testing suite. Yes, only now you have a free version which actually is acceptable to use in a professional enviroment (Express editions had too many commercial license problems), but the last 15 years you had to upgrade every 2-3 years if you wanted to use the latest features..

But just like there is still unmanaged C(++) in the latest version of Visual Studio, why not also have an unmanaged (classic) VB...

I'm an engineer: VB6 programs work fine in Windows 10 by Kevin Matney

I've been working with VB.Net for a few years, but still maintain (and update with new features!) a lot of VB6 programs. I was pleased that all of my VB6 programs work fine in Windows 10, so that's another 10 years I'll be working with VB6. . One thing I absolutely miss in VB.Net is having out-of-process servers - a rock-solid way for VB6 users to get multi-threading. I have to work with some shaky .Net EXE servers (not my code) and when they crash, my program crashes. To solve this I had to write a VB6 COM wrapper. VB6 to the rescue again.

I'm an engineer, and a self-taught programmer, and was (is) able to do some amazing things with VB. With VB.Net, I spend more time on Google than I do writing code. In fact, I would have been dead in the water if I wasn't able to search for code snippets online (and I have found the MS Help online to be the least useful - not very many examples).

I find it frustrating that Microsoft must be spending time and effort creating obscure languages like LightSwitch or F#, when it seems obvious that VB7 would be way more popular. I have forced myself to do new development in VB.Net, but the keyword is "force". I hate it, but at least with Google's help I can get things done.

I could go on and on...

Microsoft has "tried" to ignore the VB6 demographic but that is just a recurring miscalculation on their part.

Just curious, how many posts need to happen here before Microsoft will act on updating VB6?

Many of us like the idea of simply incorporating VB6 as part of the OS for current and future Windows versions. That may allow MS to save face if that is any kind of road block for them.

Microsoft has "tried" to ignore the VB6 demographic but that is just a _recurring_ miscalculation on their part. VB6 is bigger than any vision they had\have for it. It does not perfectly fit into a senior stock holders pigeon hole. Kinda like trying to squish soap in a shower with your foot. Very illusive. That seems to confuse their decision makers.

I think the Star Trek analogy is 100% accurate. Here is the truth Microsoft: we are not going away! Please align your business model to THAT fact. Thank you.

A comment by: JillS

Bill Gates PhD thesis on Visual Basic 6.0 (Anno Domini 2015)

Bill Gates PhD thesis on Visual Basic 6.0 (Anno Domini 2015):

http://www.docdroid.net/s87b/bill-gates-phd-thesis.pdf.html

A comment by Tim Chambers

VB6 was RAD. VB.NET is no longer the "Rapid" programming VB6 once was. The amount of hoops to jump through, reinventing the wheel, obfuscated code and horrible data methods drive programmers crazy. The problem is the people making the decision never used the programming languages & tools and no deep understanding of "what", "how" and "why". 
They may believe the marketing and finance people more than the expert users. If Microsoft don't believe there could be a future for VB6 and no benefit in keeping the tools then there shouldn't be any problem with selling or gifting it to the community. If your 16 year old car had travelled >200'000 Miles, rust, holes in the dash/carpet/upholstery and you thought it wasn't worth maintaining then would you mind your 16yr old son from driving it or converting it to a rally car ?? If you want to keep it then look after it, if it's not worth keeping then give it way or sell it for scrap. That goes for VB6 : If they think the Intellectual Property (IP) is so precious then keep it and update it; if the IP is not precious then MS won't loose much if they give it away or sell it for cheap. Once it's opened up or sold then if it has no value then no one else could make a profit from it and MS looses nothing. What is MS afraid of ? Are they scared that people outside of MS are actually better at efficient and creative programming, better at designing user friendly software and better at keeping customers happy ? Microsoft should stop complaining about bad customers hurting MS staff feelings and concentrate more on the wider user base instead of the PR focus group.

A comment by Charles Martel

The overarching theme here, in most all of MS’s products since about 2002, has been lack of concern for user productivity. The abandonment of VB6, I would argue, is simply the most serious and hurtful example. One can see this easily in Win8 and the hours we wasted looking for ways to do things that used to be obvious ( imagine my clients reaction if I did that to them in my custom software !). The Office ribbon forced on us with no alternative is another obvious example; a concern for user productivity would have demanded a toggle be given us so we could use the text menus if we wished. The loss of the Access 2003 data base window in Access 2007 and on is another egregious example. I have scores of others as I use the whole range of MS products. The cause may have been stack ranking – I suppose it’s a moot issue now, the damage being done. I had hoped that the mea culpa seen in the return of the Start Button in Win 10 suggested a company wide admission of all this and a willingness to consider user needs over company hubris – but there’s no sign of it here. 
Gentlemen at MS, if you read this: VB6 *WORKED* ; it allowed us to get good work done quickly. If you guys are not working programmers in the real world then you cant know what I’m talking about – and so I will not bother trying to explain what made it so much better than VB NET, but I can ask you to listen to us. We are asking for our tool back. Consider too – it will make you all very popular. Maybe you’ll get a raise and promotion.

Must read articles: written by Jonathan Allen

Must read articles:

Visual Basic 6: The Looming Crisis:

http://www.infoq.com/news/2014/04/VB6-Crisis


Visual Basic 6.0 to be Supported on Windows 7:

 http://www.infoq.com/news/2009/03/vb6_on_win7


Visual Basic 6 Renewed to Run on Windows 8:

http://www.infoq.com/news/2012/02/vb6_supported_on_win8


Visual Basic 6.0 Still Widely Used:

http://www.infoq.com/news/2009/02/vb6


Reactions to the VB 6 Open Source Rumor:

http://www.infoq.com/news/2011/05/VB6-Rumors


Is There a Future for VB.NET?:

http://www.infoq.com/news/2009/06/Future-VB.NET

Visual Basic 6 (VB6) - community protest !

Visual Basic 6 (VB6) - community protest !

Internet Trolls never die !

Trolls never die ! Trolls are bizarre creatures and dangerous for the truth ! It seems that Microsoft has hired such monsters to comment against Visual Basic 6.0. All the VB6 community has one message for them, a message that reveals their ancestral roots:

 

The disinformation propaganda on the real situation regarding Visual Basic 6.0 in 2015

A message from Vorlon:

I am an analyst and programmer, I know most programming languages and I am also a VB6 lover (and I say with great pride):

Analyzing the text messages it seems that Hman and "that" Anonymous are one and the same. Hman may be Paul Yuknewicz ! yes, him.There is pathos in this for Paul, because he advocated .NET in 2001 from what I understand.

If these comments against Visual Basic 6.0 appeared for several weeks, this means that all the struggle for VB6 comeback has a serious echo inside Microsoft. We see a lot censorship and VB6 ideas rejected on uservoice.com without explanation. Why do you think?! If you/we quit now, you/we are f o o l s.

In all the negative posts you will see an increased frequency (a pattern) of words: "patheti.c", "delusiona.l", "period.", "Again,", "case closed.", "childish", "spamming", "VB6 is dead" or "switch from VB6 to .NET" and so on. These words enter in a single pattern, belonging to only one man! Folks, just a simple idea posted here has 11,000 votes and 3,100 comments, THAT IS HUGE and really annoying for .NOT preachers (based upon common words and the style of the messages, I counted four . NET preachers across the Internet).

In order to discourage the VB6 community, they (Paul Yuknewicz and the orchestra) applied the same tactics in 2008. They employed about 3 or 4 people to negatively comment on the internet with regard to VB6, and it worked ! But Microsoft has other smart people who are pro VB6, which realize the importance and the size of the VB6 community.

Just imagine what happens-to Paul if Microsoft decides that VB6 must return ... ! it begins to have no role there, that is the real problem for him.

So, do not be discouraged or fooled by these messages, behind them is just one single man. The "negative comment" method worked from 2002 until recently, but the world begins to be smart !

PS: this article is also of interest: 

When will Microsoft stop the mockery ?!

Visual Basic 6.0 machine:

Paul Yuknewicz without orchestra:

The .NET preachers:

Visual Basic 6.0 vs Visual Basic .NET - job trends !

Visual Basic 6, Visual Basic.NET Job Trends

Visual Basic 6 jobs - Visual Basic.net jobs

Recently hundreds of programmers were censored on uservoice.com !

Recently tens or hundreds of programmers were censored on uservoice.com. Many of us do not have the right to free speech on that site. One of the programmers who remained uncensored is VBfire (they forgot to censor him, fortunately!)
On that page (1) VBfire commented: There is no another uservoice page to have more comments and more real votes than this one.  Someone said that we pray for Microsoft to release another version of VB6. I would say that we force Microsoft to pull a new version of VB6. What we do here is by no means a petition, is more of a clear demand ! The VB6 community has past the point of petitions and requests when it comes to Microsoft. Even the two uservoice administrators that make fun of tens of thousands of people (who actively are campaigning for VB6) will shortly be accountable for their conduct on behalf of Microsoft. Do not think that the repeated rejection of an idea supported by a huge mass of people will be wiped with a sponge and nobody will notice this.

1. http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/3440221-bring-back-classic-visual-basic-an-improved-versi

Text analysis on Paul Yuknewicz message

Paul Yuknewicz writing:

”We have read all of the comments on this thread and I’d like to thank you for providing your constructive feedback on this issue. Instead of merely repeating our support and migration guidance that has been laid out on http://msdn.com/vbrun, I’d like to address some of your specific comments here. To play back the feedback themes we’re hearing: - VB6 is awesome - VB6 needs to be brought forward and maintained: in a new release or OSS VB6 was and still is without a doubt awesome. VB6 made developers incredibly productive building a breadth of applications and as a result we have a wealth of applications and passionate developers to this day in 2014. One way I see our mission in developer tools is to empower developers to solve problems. This includes both today’s problems AND the problems of tomorrow. VB6, as you all have stated repeatedly in this thread, is an excellent tool for solving the problems of its day. We also stand behind our decision starting in 2002 to meet the current demands of our developers and the industry with .NET. For the scenarios VB6 set out to do, we see VB6 being “complete”. We feel good about VB6 being able to continue maintaining their applications for the past 15 years. Current needs ranging from distributed applications and services, to web applications and services, to devices, to new architectures and languages, required fundamental changes to the whole stack. We looked at how we could accommodate these needs through incremental changes to VB6 while maintaining its essence, and that was not possible. To address the modern needs we would need to go far beyond updating the language. We have to remember that VB6 is not just a language. VB6 is a language, a runtime, a platform library, a tool/IDE, and an ecosystem tightly packaged together in a way that made all of them work well together. We’ve worked with many customers on migration from VB6 to .NET and found that while yes, there are language changes, the dominating factor in migration difficulties isn’t the language differences. Even open sourcing the language/runtime wouldn’t solve the fact that VB6 was thought for a different set of problems, and the fact that its strength came from the end-to-end solution provided by all these five pieces working together. Take a change like 64bit, the complete runtime, tools and ecosystem chain would need to be retooled. So, moving forward what can we do? Where we have been able to help move forward is in our stance around support and interoperability. The VB6 runtime it is still a component of the Windows operating system and is a component shipped in Windows 8.1. It will be supported at least through 2024. This ensures your apps and components continue to run as you incrementally move forward to .NET. The support policy is here: http://msdn.microsoft.com/en-us/vstudio/ms788708. There are numerous interop strategies that we developed and evolved to enable incremental migration as you upgrade your skills, described here: http://msdn.com/vbrun. In summary, VB6 was awesome. We agree. We don’t expect or demand anyone to throw away their code or rewrite from any of our technologies unless it makes business sense for them to do so. We have to innovate to enable our customers to innovate. It is not a viable option to create a next version of VB6. We stand by our decision to make VB.NET and the .NET Framework. We think they are awesome too. It is not feasible to open source VB6 tools chain and ecosystem. The VB6 runtime was last shipped in Windows 8.1 and will be supported for the lifetime of Windows 8.1. Support and interop are great tools to move forward incrementally. I hope you feel we’ve listened to your feedback and that I’ve explained things well enough that you understand our decision. Paul Yuknewicz Group Program Manager Microsoft Visual Studio Cloud Tools”

Analysis on Paul Yuknewicz message:

Frequency and top words :

Word	Occurrences	Frequency	Rank
our	9	2.4%	1
language	6	1.6%	2
you	6	1.6%	2
net	5	1.3%	3
forward	5	1.3%	3
your	5	1.3%	3
runtime	5	1.3%	3
tools	5	1.3%	3
applications	5	1.3%	3
problems	5	1.3%	3

2 word phrases frequency :

Expression	Expression count	Frequency	Prominence
we have	5	0.8%	57.1
and the	4	0.6%	49.8
applications and	4	0.6%	73.6
windows	3	0.5%	12.5
it is	3	0.5%	17.3
move forward	3	0.5%	20.5
is not	3	0.5%	24.8
as you	3	0.5%	41.4
support and	3	0.5%	43.2
http msdn	3	0.5%	45.8
for the	3	0.5%	46.8
the language	3	0.5%	48.6
vb6 was	3	0.5%	49.5
vb6 is	3	0.5%	65.8
to	3	0.5%	73.5
to innovate	2	0.3%	13.3
be supported	2	0.3%	16.4
will be	2	0.3%	16.5
in windows	2	0.3%	17.3
shipped in	2	0.3%	17.4
to enable	2	0.3%	17.6
vb6 runtime	2	0.3%	18.9
the vb6	2	0.3%	19.1
and ecosystem	2	0.3%	21.8
here http	2	0.3%	22.5
net and	2	0.3%	28.7
a component	2	0.3%	30.7
have to	2	0.3%	34.6
there are	2	0.3%	35.2
to net	2	0.3%	36.9
our decision	2	0.3%	41.5
to do	2	0.3%	41.9
is a	2	0.3%	41.9
fact that	2	0.3%	42.6
the fact	2	0.3%	42.8
of our	2	0.3%	43.7
need to	2	0.3%	46.8
would need	2	0.3%	46.9
that vb6	2	0.3%	49.2
able to	2	0.3%	50.8
a language	2	0.3%	53.8
com vbrun	2	0.3%	56.1
msdn com	2	0.3%	56.3
problems and	2	0.3%	59.8
changes to	2	0.3%	61.1
to be	2	0.3%	62.4
services to	2	0.3%	64.2
and services	2	0.3%	64.3
of the	2	0.3%	64.5
vb6 being	2	0.3%	68.1
in a	2	0.3%	69.2
all of	2	0.3%	74.2
to address	2	0.3%	74.7
problems of	2	0.3%	75.6
the problems	2	0.3%	75.7
in	2	0.3%	76.6
developers to	2	0.3%	80.1
of applications	2	0.3%	82.8
this thread	2	0.3%	86.3
vb6	2	0.3%	87.6
like to	2	0.3%	94.3
i’d like	2	0.3%	94.4
on this	2	0.3%	96.4

Details of Writer: 39 year old Male
Date/Time: 9 February 2015, 1:10 pm

LIWC Dimension	Your Data	Personal Texts	Formal Texts
Self-references (I, me, my)	4.32	11.4	4.2
Social words	7.90	9.5	8.0
Positive emotions	2.83	2.7	2.6
Negative emotions	0.30	2.6	1.6
Overall cognitive words	5.96	7.8	5.4
Articles (a, an, the)	6.41	5.0	7.2
Big words (> 6 letters)	26.23	13.1	19.6

The text you submitted was 671 words in length.

---

Reading Text ...

Reading Ease

A higher score indicates easier readability; scores usually range between 0 and 100.

Readability Formula	Score
Flesch-Kincaid Reading Ease	67.8

Grade Levels

A grade level (based on the USA education system) is equivalent to the number of years of education a person has had. Scores over 22 should generally be taken to mean graduate level text.

Readability Formula	Grade
Flesch-Kincaid Grade Level	7.2
Gunning-Fog Score	10.8
Coleman-Liau Index	10.7
SMOG Index	8.2
Automated Readability Index	6.7
Average Grade Level	8.7

Text Statistics

Character Count	3,047
Syllable Count	999
Word Count	676
Sentence Count	49
Characters per Word	4.5
Syllables per Word	1.5
Words per Sentence	13.8