Which version of VS .NET do you use for C
Printed From: Codejock Forums
Category: Codejock Products
Forum Name: Suite Pro
Forum Description: Topics Related to Codejock Suite Pro
URL: http://forum.codejock.com/forum_posts.asp?TID=5411
Printed Date: 21 November 2024 at 7:26pm
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com
Topic: Which version of VS .NET do you use for C
Posted By: SuperMario
Subject: Which version of VS .NET do you use for C
Date Posted: 02 November 2006 at 9:57am
|
Hello all, we are trying to get an idea of witch version of Visual Studio .NET C# and VB.NET developers are currently using. Does anyone still use Visual Studio 2002? What features do you expect from a .NET component? Thank you for your participation  |
Replies:
Posted By: fantama
Date Posted: 02 November 2006 at 3:08pm
| VS 2005 |
Posted By: ABuenger
Date Posted: 02 November 2006 at 5:17pm
|
Definitely VS2005 and .NET 2.0 I'm also not sure if I'm interested in a WinForms toolkit, I would only switch from MFC to WPF, from MFC to WinForms is pointless in my eyes. Also what is with C++/CLI? ------------- Codejock support |
Posted By: Shragel
Date Posted: 02 November 2006 at 6:48pm
| Only using VB6 |
Posted By: JamesH
Date Posted: 06 November 2006 at 12:20pm
| Using VC 6! We switched over to CodeJock from Infragistics specifically because they stopped supporting their ocx controls... |
Posted By: Shragel
Date Posted: 06 November 2006 at 2:15pm
| Hopefully its not going to happen here. |
Posted By: SuperMario
Date Posted: 06 November 2006 at 4:34pm
No, it won't happen here
|
Posted By: Shragel
Date Posted: 06 November 2006 at 6:58pm
| Thats good. We invested alot of time in this because its still in com. |
Posted By: tobi
Date Posted: 08 November 2006 at 5:15am
| I would expect a control suite with same functionality of XtremeToolkit to ease porting ! Design time designers would be great !!! |
Posted By: fwhite
Date Posted: 13 November 2006 at 3:55pm
| VC 6, and hope to continue to do so. |
Posted By: EdwinSchild
Date Posted: 20 November 2006 at 5:30am
| Docking is the most important feature since that is missing in WinForms |
Posted By: MNovaro
Date Posted: 24 November 2006 at 5:40am
| Right now, VB6 only |
Posted By: hipopotamo
Date Posted: 14 December 2006 at 2:00pm
|
Hi, We still use Visual Studio 6.0.
My answer is 2002.
But I pool the wrong one. 2005 :-(
|
Posted By: hipopotamo
Date Posted: 14 December 2006 at 2:11pm
|
Hi again,
The main reason we choose CodeJock its because VC 6.0 support
 So it would be very, very sad news if Codejock stop supporting this platform
 Regards
|
Posted By: Philip
Date Posted: 20 December 2006 at 8:12pm
|
Visual Studio 6.0
The costs in higher versions are grater than the benefits (high resources needed, slow running).
Our clients don't pay us for .Net, they pay us for fast solutions to their needs, and vb6 can do it for the next 10 years. ------------- BORG Design - Sultanescu Philip |
Posted By: flauzer
Date Posted: 22 December 2006 at 12:08pm
|
Visual Studio 6.0 (only) for Windows programs
VS2005 and .NET 2.0 for WEB
|
Posted By: tommylov
Date Posted: 09 January 2007 at 2:53pm
| Yes, I'm still using VS2002. |
Posted By: asifimam
Date Posted: 31 January 2007 at 3:15am
|
VS-2005 for both 32 and 64 bit platforms.
------------- Debug till Nobug |
Posted By: EdwinSchild
Date Posted: 31 January 2007 at 5:19am
|
We didn't renew our maintenance because Codejock couldn't make any statement about 64-bits and we desperately need it. |
Posted By: Simon HB9DRV
Date Posted: 31 January 2007 at 6:16am
|
FWIW I use Visual Studio 6.0 with C++, I hope this will be supported for a long time to come (please).
------------- Simon HB9DRV |
Posted By: SuperMario
Date Posted: 01 February 2007 at 12:20pm
Use VS 2005 to compile in 64 bit. It will work. |
EdwinSchild wrote:Posted By: EdwinSchild
Date Posted: 01 February 2007 at 1:12pm
Very good idea. 
|
Posted By: Shragel
Date Posted: 01 February 2007 at 3:13pm
| :) |
Posted By: fabioraciti
Date Posted: 05 April 2007 at 12:54pm
| vc2005 |
Posted By: daveED
Date Posted: 10 April 2007 at 6:52am
| VB 2003 & now using VB 2005 |
Posted By: joeliner
Date Posted: 10 April 2007 at 8:24am
|
Visual Basic 6.0(since we have to support our existing systems) rolling over to VS 2005 for all our new products. ------------- Product: Xtreme SuitePro (ActiveX) version 13.1 Platform: Windows XP SP 3 Language: Visual Basic 6 SP6 |
Posted By: JohnCrenshaw
Date Posted: 10 April 2007 at 3:06pm
|
I'm using VS 2005 but I have some strong feelings on this issue. Companies that don't HAVE to use 2005 (for Unicode debugging or something) are wise to stick with 6.0. 2005 was a HUGE step backwards, and ultimately decreases efficiency. Many key features that worked great in 6.0 vanished sometime before 2005 made it out the door and made things much worse.
|
Posted By: gshawn
Date Posted: 10 April 2007 at 9:21pm
| VB 6.0 for all existing products, VS 2005 for one or two new ones |
Posted By: yair-edsoft
Date Posted: 14 April 2007 at 11:43am
We are using VB6.0 
New Product VS2005 ------------- yair |
Posted By: yair-edsoft
Date Posted: 14 April 2007 at 11:43am
|
We are using VB6.0
New Products VS2005 ------------- yair |
Posted By: Raver
Date Posted: 13 June 2007 at 1:32pm
| VC 6 |
Posted By: Metodo_Sviluppo
Date Posted: 20 June 2007 at 4:04am
| VB6 |
Posted By: Rhogan
Date Posted: 26 June 2007 at 9:32pm
| Pure C++ using VS2005 |
Posted By: faizullah
Date Posted: 03 August 2007 at 10:27am
| We are using visual studio 2003 and using vb.net. But I couldn't make the skinframe working in vb.net form. Do you have any sample code to do that? |
Posted By: SuperMario
Date Posted: 10 August 2007 at 12:00pm
You can do something like this, just make sure the styles folder path is correct: Private Sub frmMain_Load(ByVal eventSender As System.Object, ByVal eventArgs As System.EventArgs) Handles MyBase.Load Dim skinFolder As String skinFolder = System.IO.Path.GetDirectoryName(Application.ExecutablePath) + "\..\..\..\Styles\" SkinFramework.LoadSkin(skinFolder + "Office2007.cjstyles", "NormalAqua.ini") ... ... ... End Sub Private Sub frmMain_VisibleChanged(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.VisibleChanged If Me.Visible Then SkinFramework.ApplyWindow(Me.Handle.ToInt32()) Me.BackColor = SkinFramework.GetColor(XtremeSkinFramework.XTPColorManagerColor.STDCOLOR_BTNFACE) End If End Sub |
Posted By: dlt123
Date Posted: 20 September 2007 at 12:18am
|
Well I guess I am using Visual Studio 2002 since I am using Visual C++ Studio 6.0 Professional... which brings me to a question I've been pondering. I am learning VS C++ and bought VS 6 Pro a couple of years ago. I never got around to learning C++, but am now. Should I consider getting Visual Studio 2005 Pro, if so why? I would rather take the funds and get the CodeJock Xtreme ToolkitPro. Is VS 2005 that much better then VS 6.0? Am I missing something because I am using VS6.0... accept my brain?...  Thanks, Dennis ------------- Belief has no affect on reality. |