Visual Basic Future

Home

Downloads

Discussions

People

License

RSS

All Resource Updates

Discussions

Releases

Wiki

RSS Feed

RSS

Comments \| Print \| Page Info \| Change History (all pages)	Search Wiki:
Home
Resource Page Description Samples and documents describing Visual Basic 10.0 language and IDE features. Visual Studio 2010 Beta2 Samples are now live! Samples and documents for Visual Basic 10.0 can be found on the Downloads page. Please see the walkthroughs that ship with Visual Studio 2010 Beta2 for additional information about these samples and the new features for the Visual Studio 2010 preview. Please submit bugs through connect, or provide comments in the discussion section of this site. It is important to remember that the code shown here is preliminary, particularly any code that might touch on the 2010 features, and is designed to run with a very early, beta version of Visual Studio 10.0. This code may not work correctly, and the syntax shown in this code may change before VS 2010 is released. The Office example ought to run smoothly if you have a copy of the most recent version of Microsoft Office installed. It may also work with older verisions of Office. The Python example will work if you download IronPython 2.0 . It may also work with more recent versions of IronPython. You will need to replace the IronPython, IronPython.Modules and the Microsoft.Scripting assemblies found in the references section. Right click on the References node in the Solution Explorer and choose Add Reference. Browse to the directory where you installed IronPython and add the missing Assemblies. By default, IronPython is installed in the Program Files directory. Please come back here later for additional information about the Silverlight example. Thank you for your interest in Microsoft products.
Last edited Oct 20 2009 at 5:23 PM by JonathanAneja_MS, version 12
Comments Support wrote Nov 28 2008 at 12:51 PM One thing that I think that could be a great feature in VB 10 or newer, if standart symbol & (ampersand) with _ that uses in sting concatination would be replaced how is done in C# using symbol before double quates @".. ", so then in VB looks like that for example: * that in old VB style: "Hello " _ & " world" * changed to that style: @"Hello world" This very helps for all developers who uses more then one line text in strings and was readable more easy. jamiebalfour wrote Dec 3 2008 at 9:04 PM There should be new controls, such as 3D modeling tools. There should also be a .avi player in the control collection. I also think there should be snippets and code support for a spell checker. Possibly a really good feature to include would be a fully functional page word processing control like TX Text control, and also the ribbon control. yakshasa wrote Dec 4 2008 at 2:49 AM I agree that there should be a version of the Office Ribbon Control available directly in VB. Vermiculus wrote Dec 6 2008 at 11:36 PM I agree, yakshasa, and i also think it would be great if there were chart and graph controls as well, similar to Excel Lonewind wrote Dec 11 2008 at 2:37 PM Can we also integrate even just some of the features of expression blend to VB? i'm more particular to the storyboard or animation whenever there are instances at VB such as mouse hovering, clicking and others as well. Fduch wrote Dec 12 2008 at 2:07 AM looks like Microsoft is abandoning VB.Net. The statement lambdas and multiline lambdas were in C# for 3-4 years. All other "features" are C# ones too. For the same 3-4 years C# has had yield return keyword that was used a lot while creating LINQ. You cannot efficiently create LINQ classes in VB.Net. And now they say they are not going to make iterators available even in VB10. If you want to try to 6tell them they are wrong vote for these bugs/suggestions on Microsoft Connect website: https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=354841 https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=381572 jjthebig1 wrote Feb 1 2009 at 7:46 AM MULTIPLE INHERITANCE, MULTIPLE INHERITANCE, MULTIPLE INHERITANCE. Please add multiple inheritance to VB. Also, if you have a chance, please fix the issue with DatetimePicker as a ToolstripControlHost. mavstar wrote Feb 2 2009 at 3:16 AM Please reconsider adding the Yield Keyword. It is essential for taking advantage of the CCR (Concurrency Coordination Runtime). For VB to truely keep up with C# easy Asynchronous Programming is a must-have Ondrej wrote Feb 2 2009 at 8:33 AM Ribbon UI controls in Windows Forms are needed. Mohammed1985 wrote Feb 7 2009 at 11:57 AM I agree with Fduch. comparing with other microsoft language such as C#.Net and C++.Net, VB has many limitation. since vb6 there was a chance to use pointer using VarPtr, StrPtr, ObjPtr since the realse of VB 2002 (VB 7.0) they become unsuporrted, but in the other hand C# 1.0 has come with unsafe code that allows you to use pointers at your own risk now VB is in version 9 and yet this feature is unspoorted to VB Developer so it will be nice if VB has the ability to use pointers even with some limitation but in any way it will exist in VB and it will open for us (VB Developer) a new way to think in our code. robains wrote Feb 15 2009 at 8:29 PM Pointers ByRef ?? Not sure what you mean it doesn't have ability to use pointers? This has been around for a long time in VB. My Requests: 1. Please speed up the VS IDE -- be it with C#, C++, or VB -- any forms containing many controls (200+) becomes incredibly slow for object renames. 2. DirectX support native. 3. Easy multile CPU assignment support for worker threads. 4. No interest in WPF unless it's fully integrated in the VS IDE without bugs/issues -- companies that separate UI coders from business logic is more a rare case than the norm -- companies just can't afford to have that many "task specific" developers these days, keep focused on a single intregrated development solution from UI to backend to business logic. Rob Mohammed1985 wrote Mar 1 2009 at 3:24 PM int x = 20; unsafe { int* y = &x; y = 30; } above code is unsafe code in c#. all i hope is to write some thing like this: Unsafe Dim x as integer = 10 Dim y as Integer = &x *y = 50 End Unsafe Beastly_Hacker wrote Mar 19 2009 at 5:55 PM 1) Its recommended to include the CR2008 Components with the package . 2) fix the problem's details that occur when assigning a Vista icon to a form .... ( 2 days of fighting with VB.NET to resolve the problem ) boneoh wrote Apr 11 2009 at 8:56 PM I agree with Fduch. VB has been given second class status by Microsoft. C#? No way. Time for me to get serious about other platforms and toolsets. Adobe Flex and AIR are looking better every day. jasonlives009 wrote Apr 18 2009 at 9:35 AM The worst thing that Visual Studio.net contains is that its code is easily de-compiled. Where as the visual studio 6. code cannot be fully de-compiled. Please make such a compiler that create native machine code instead of creating MSIL. A Programmer creates a application in many days and months yeilding high efforts and labour. But if someone else de-compile the application code than what's the use of such a big software. ( Microsoft Visual Studio.Net ) Visual Studio.net creates MSIL Code. and not the native code. Even we can read the exe without de-compiling... Its in plain english. Is there any method to protect the .net code. Is there any method to convert MSIL to Native Code. So that the application developed in .NET cannot be decompiled. If so. please include in VS10. NJKA wrote Jun 22 2009 at 8:53 AM As Mohammed1985 wrote, When oh, when is the glass ceiling going to be removed from VB.Net. Time and time again I find myself needing Unsafe code blocks that can directly access and use pointers. And no this has nothing to do with passing objects ByRef. regnwald wrote Aug 23 2009 at 5:11 AM This thread must almost be out of date. But presumably someone will still read a new posting. Also, since beta1 is already out you can only react now to bugs rather than bad design. Nevertheless I must express my extreme dismay at the abysmal treatment of VB pointers. They are the crux to any inventive programming. There are three needs for effective use of pointers: GetThem, somewhere to SetThem and somewhere to safely retain them. In VB5 I had all three for some needs (arrays, user types and some other structures) and used classes with static objects when needed. I bought VS2005 and threw it out!! I cannot for the life of me understand WHY MS should be so irresponsible. With the bragging of a CRL why the devil is it that C++, C#, J# and VB do not yet have a common access to the same language elements. As someone said "We should all be playing in the same sandpit." The trouble is that we all have too little power, and too little voice. Too few alternatives. I explored Delphi and C++ with CodeGear and found it wanting. As a consequence we ordinary folk spend our nights playing with ourselves instead of trying to change things. And that leaves you MS guys free to play with yourselves. Thats all well and good and private but wasteful. But when you in MS start playing with ME I get offended. For all our sakes, please give ALL OF US stable methods and common syntax to GetThem. You've got access to Them! For all our sakes, please give ALL OF US stable structures with common properties at which to SetThem. For all our sakes, please forALL OF US, if you have to change a structure INCLUDE the old structure as a field within the old. NO - I WILL NOT BE BUYING VS2010 for the same reasons I did not buy VS2008 and THREW OUT VS2005. I'll get by with VB5 and ASM for the difficult bits (After all, thats where I at 72 had to start). Why do I hang on to VB? Its the only worthwhile language that properly defines its code loops. IF..ELSE..ENDIF; Do..WHILe etc compared with a forest of {..}. Only FORTRAN defines loops more definitively. DO 100.. ..100 CONTINUE. Even PASCAL (DELPHI) uses END; but only sometimes and too often. Why is that important? It leads to easy, faster and accurate reading and so less confusion in 'over the page(s)' code 'lines', fewer coding errors and faster coding. It has been worth the price in the past, but with poor backward compatibility it is not worth the cost of continued upgrading. But now it looks as though I'll not be incurring that expense until at least 2013, if then. Well, did anyone important get this message? Perhaps I should expand this more and send it to the shareholders Joacim wrote Sep 7 2009 at 2:51 AM >looks like Microsoft is abandoning VB.Net. The statement lambdas and multiline lambdas were in C# for 3-4 years. All other "features" are C# So? What's your point? What new features does C# 4.0 get? Oh, optional parameters... Great! They have existed in VB since 1995 with the release of VB4. What else is new, late binding.... In VB since version 1. So is Microsoft abandoning C# also because it doesn't have all features VB have? C# will not get XML literals, in my opinion the best feature since intellisense. :) jimmyfluore wrote Jan 16 at 3:10 PM Dim i(10) As Integer Unsafe Dim p As Pointer(Of Integer)'Declare a pointer of integer p=New Pointer(Of Integer)(i)'Let p point to i(0) p+=1 'Let p point to i(1) p.SetValue(100) 'Let i(1)=100 Msgbox(p.GetValue()) 'Output i(1) End Unsafe Sign in to add a comment

Updating...