|
Sorry but I disagree with that, VB6 may be unsupported but it certainly isn't dead and I suspect there may be more people using it for development, or at least maintenance, than there are using VB2008
Maybe I am sensitive as I also still develop in VB6. I would upgrade the existing code if only it was more straight forward to do so
In answer to the original poster
The client in my system keeps a record of the last server it logged in to in a local file and if it doesn't have the file (a new installation) it allows the user to enter the name of the server and then saves it on a successful connection and on subsequent executions it shows what it used last time and the user is only required to put it in once
Not quite what you were asking for but hopefully helpful
|
|
|
|
|
Mike Deeks wrote: Sorry but I disagree with that, VB6 may be unsupported but it certainly isn't dead
It just hasn't fallen in the grave yet, but it's standing at the edge, clutching it's chest, just like it should be.
Mike Deeks wrote: I suspect there may be more people using it for development, or at least maintenance, than there are using VB2008
Probably true. That still doesn't change the fact that starting any new development in VB6 is a complete waste of time and resources. Microsoft is killing the runtime off from any future versions of Windows. Sure, the runtime may still work, but only by chance, not by choice.
Kill it. Kill it. Kill it. I don't want to here a bunch of whiny people complain that their apps don't work any more like there was when Vista came out. VB.NET came out 10 years ago. There's no longer any excuse for continuing to cultivate old technology that has LONG since been replaced.
|
|
|
|
|
Hmmmmm 10 years ago, and still people are using it, VB6 must be really good 
Or maybe it is because there was no straight forward way to take projects consisting of many thousands of lines of code and expect it to work in the .net environment without a significant amount of testing and change
At least with Office 2010 I can still open and use virtually any document that has been constructed in the previous versions
I am interested to hear that there is a strategy to stop people from using programs that were developed too long ago, I must have missed the "best before" date on the packaging.
As there is no excuse I will try not to whine too loudly about it especially where you might hear...
|
|
|
|
|
Mike Deeks wrote: I must have missed the "best before" date on the packaging
You did. The runtime wasn't supported on Vista until a bunch of people started crying about it. MS went through a bunch of pain to get it to work on Vista. Since 7 came out pretty quick to replace the debacle that was Vista, 7 also supports the runtime. But that's as far as it's going. There will be no VB6 runtime support in Windows 8 (or whatever it's called). Good luck keeping your VB6 apps working.
|
|
|
|
|
Hi
Im totally confused with Assembly Version vs Publish version.
I have a windows application.I use a SetupProject --> rebuild it --> ,I get the MSI file and Install.
I am trying to do a Auto Update on the application and would probably have to play with the version numbers in order to do this.
My 1st problem is, when I change the applications assembly version and install the new msi - I get an error that there is already a application installed with the same version, but when I change the publish version it uninstalls the installed app and install the new one.
My 2nd problem is I dont really know the best way to check if a new version is available.
My idea is to take the running apps version and compare it with the version of the msi file on the server.If they are not the same, it will popup a message on the application saying "A new version is available, please click yes to install the new version"
What I want to know:
1.How do I get the application to work on the assembly version and not the publish.
2.I would really appreciate tips what is the best way to write an auto update check.
Thank you everyone
|
|
|
|
|
We had the same problem, and finally decided to write a small AppVersion.exe that checks a local AppVersion.txt and compares it to the server's AppVersion.txt - if different, it shows a message informing the user that an update is being installed, installs the update from the server, and replaces the local AppVersion.txt from the one on the server. Whether an update was done or not, AppVersion.exe starts a process of the main application and then closes.
The only implementation problem we had was changing all the desktop icons to point to AppVersion.exe instead of the main program.
|
|
|
|
|
hi friends
i want to create a setup project that instal my app and MSDE in vb.net 2008
can you help me please?
M.Alizadeh
|
|
|
|
|
|
my sql is sql server 2000
and in some article i read that i should install msde
do you think installing sql 2005 express is enough ??
M.Alizadeh
|
|
|
|
|
I think SQL Server Express 2005, is the earliest supported version. ideally you should go for SQL Server 2008 express.
|
|
|
|
|
Hello,
Has anyone else had problems opening files on network drives through VB.NET programs using Windows 7? The error on my local machine says:
'(correct path taken out)' could not be found. Check the spelling of the file name, and verify that the file location is correct. If you are trying to open the file from your list of most recently used files on the File menu, make sure that the file has not been renamed, moved, or deleted."
I deployed the program on a windows XP machine and it worked fine.
Any ideas as to what windows 7 security settings that need to be changed?
Thanks!
|
|
|
|
|
Open the path using Explorer - does it ask for a username/password combination?
I are Troll 
|
|
|
|
|
No password needed but i think something is set up on log in for access to the network drive so i should have access under my login.
Thanks for the reply
|
|
|
|
|
It is definitely a security issue. Are these windows programs or ASP.Net Apps?
|
|
|
|
|
|
Got it to work by running visual studio NOT in Administrator mode and then rebuilding/installing. Seems the run as administrator has some sort of effect on the end build. Anyone else run into this?
EDIT: This still doesn't work on a different deployment machine running on Windows 7, only on mine.
modified on Friday, July 23, 2010 12:18 PM
|
|
|
|
|
|
Bump what? Post bumping does no good around here.
|
|
|
|
|
I have seen other problems caused by using "Run as Administrator" for example: One of my programs automates outlook and if I use run as administrator then it fails to automate outlook with a strange error
I have no idea why and as it works when run normally I haven't investigated further
|
|
|
|
|
Thanks for the reply!
Yea, seems websites on the local IIS need to be ran as administrator, but doing this with projects causing some issues. Yay for Windows 7 security issues.
|
|
|
|
|
Hi
I haven't been programming for a while, nearly 3 years. So I thought I should refresh my programming knowledge. Last time i did something with vb.net was with Visual studio 2005. But now I have VB.net/VS 2010 available.
How much changes have it been to the language since I last was active? Is all my old textbooks worthless, or can I use these to get up to speed again?
I've also considered to "jump ship" and switch over to C# since I might have to spend some time to get up to speed again.
Any feedback?
/Eiel.
|
|
|
|
|
You'll be fine, yes things have evolved, but it extensions to the core, so you don't have to pick them up straight away.
As for C#, you could learn that in parallel, the classes are basically identical and you will soon pick it up.
|
|
|
|
|
If I install Visual basic 2010 Express edt. will I encounter any problems if I at a later time install Visual Studio 2010 Professional edition?
Any ideas?
/Eiel
|
|
|
|
|
I wouldn't think so, but VS pro does everything + more of VB express, so i would uninstall VB express.
|
|
|
|
|
Have a look at the VB dev center and some of the articles there. they'll give you a good idea of what's new. the most important changes are around LINQ and lambda functions. Then the new stuff in VS 2010 is mostly to do with features that were in C# 3 but not in VB 9, e.g., automatic peoperties, statement lambdas.
Kevin
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
