Board index » Visual Studio » How to rename files with support wildcard ?

Visual Studio98
How to rename files with support wildcard ?


-

DOS.



VB.net is for fucking newbies









On Feb 21, 4:27 am, "ABC" <a...@abc.com>wrote:



-

On Feb 21, 6:38 am, "susie...@hotmail.com" <susie...@hotmail.com>

wrote:

susiedba -Then why are you trolling a VB group?



ABC - Look at the System.IO.File functions.

You can rename files with a "*" but be careful.





-

I'm not TROLLING.



I am ARGUING FOR THE FUTURE OF VB.



Microsoft is not taking it seriously.



FROM WHERE SELECT is not going to make it EASIER.



if you're going to force OOP down our throats; then don't make us buy

visio to use OOP.









On Feb 21, 7:08 am, "dhbernard" <dhbern...@gmail.com>wrote:





-

On Feb 21, 7:01 pm, "susie...@hotmail.com" <susie...@hotmail.com>

wrote:

I agree with you about M$ and VB support.

But you could be a little nicer to newbies.



I make a VERY good living using VB 6 thru VB.Net 2005.

It's not a perfect world but one can adapt and move forward.

Just thoughts ... Not flaming you....







-

it's just an incomplete offering.



Microsoft isn't putting 9 players on the field in a baseball match---

I can't use VB.net (it's not even called that!) in 3/4 of the places I

used to use VB6.



i can't save DTS packages as VB.net

I can't use VB.net 'scripts' in SQL Server jobs

I can't use VB.net in VBS files- does powershell _EVEN_ support VB?

I can't use VB.net for clientside DHTML

I can't use VBS for clientside DHTML in ASP.net (at least my ASP.net

book from MS Press says that-- I do have some people saying that is no

longer true)

I can't IMPORT VBS or VBA using the VB.net migration wizard

I can't EXPORT VB.net back into VB6. THIS SHOULD NOT BE A ONE WAY

TRIP UNTIL .NET IS A COMPLETE SOLUTION. INCLUDING OFFICE AND VBS AND

ACTIVEX SCRIPTS.



And I honestly and sincerely have this 'riddle' for you.. I've got

this machine under my desk; and it's got some version of the

framework. Can you please describe to me, how to determine which

version of the framework exists?



Let's talk about building a VBS file that I'm going to SMS out to

peoples desktops to figure out which version of the framework is on

machineX and jam that information into a database.



IT IS NOT PRETTY, IT IS NOT EVEN POSSIBLE.



now try to call up your 'Jr Network Admin' and to it over the phone

with someone that cant speak english.



.NET IS .NOT ON .ANY DESKTOPS

and even the ones that have it; it is impossible to determine 'which

version of the framework is on a particular machine'



TRY ME. SERIOUSLY, YOU WILL GET THIS ANSWER _WRONG_.



Marketshare of VB is not HALF of what it was 5 years ago

And my IDE crashes every single day.



I do a lot of Reporting Services development; and it's just not

getting better.



I have a laundry list of bugs in MS Access

and when MS stops selling us on the 'latest and greatest version' they

remove 'its a feature not a bug' from the vocabulary and start

replying 'yes sir it is a bug we will fix it' is when I stop this was.



As it is; they killed VB in order to invent a new language

and they're going for 'Visual Fred 3.0 ' in this next version.



Will I be able to bind a function into a SQL Statement-- like I can in

_ACCESS_ and I have been able to for the past 10 years?



seriously I take a new function 'MarketSharePercent' and I pass it a

programming language



would I be able to



Dim x as new Whatever = From ProgrammingLanguages & _

Where Relevent=1

Select ProgrammingLanguage,

MarketSharePercent(ProgrammingLanguage)



if that is going to be supported _EVERYWHERE_ then maybe I'll STFU on

the 'next version'



but i've been saying that for 5 years; and VB is roadkill at this

point.

they tried to sell us on a debugger without edit and continue, and

I'll be damned if I use one with LESS functionality



and meanwhile they KILLED the worlds most popular langauge.



I used to se one language for EVERYTHING.

I could reuse my own custom stuff in VBS, VBA, VB6, DHTML, ASP



I used to be able to create a spreadsheet - using Excel VBA -- on the

CLIENTSIDE - using simple macros.



is that possible anymore?



I don't want to hear 'yeah it is a security risk'



when they should have been fixing holes and making COM and SQL

authentication more secure.. they were too busy shoving .NET up our

asses to fix COM.



Com / ActiveX is always going to beat .NET

Mainly because it runs in more places.



and instead of FIXING SECURITY PROBLEMS; MS is trying to take us for a

ride and sell us on this .NET _CON_













On Feb 23, 7:07 am, "dhbernard" <dhbern...@gmail.com>wrote:



-

and the bottom line is that I have better things to do then spend all

my time learning a new version of VB every year.



they don't deserve to SELL US on an IDE that stops crashing

they deserver to FIX THEIR PRODUCTS and TEST THEM BEFORE SELLING THEM

OR GIVING THEM AWAY.



they deserve to NOT CENSOR PEOPLE THAT SPEAK THE TRUTH



a lot of times I really and honestly try to help people.

but my POSTS ARE BLOCKED BY M$ BECAUSE I HAVE A BRAIN AND I REFUSE TO

PUT UP WITH THEIR ABUSE.



Me talking in capital letters IS NOT YELLING.

I got FIRED at MS for using CAPITAL FRIGGIN LETTERS

I got FIRED at MS for using CAPITAL FRIGGIN LETTERS

I got FIRED at MS for using CAPITAL FRIGGIN LETTERS

I got FIRED at MS for using CAPITAL FRIGGIN LETTERS

I got FIRED at MS for using CAPITAL FRIGGIN LETTERS

I got FIRED at MS for using CAPITAL FRIGGIN LETTERS





I was working at 'MSN Quality of Service' and I had 13 bounced emails

in like a month.. Hotmail-- get this.. Hotmail would send me an email

saying 'hotmail can't find Hotmail'



I mean ROFL



my job was 'to illustrate the customer experience' and my job was

'quality of service'



AND WHAT DO I GET FOR BITCHING BITCHING BITCHING?



firing people for BITCHING doesn't FIX BUGS.

firing people for BITCHING doesn't FIX BUGS.

firing people for BITCHING doesn't FIX BUGS.

firing people for BITCHING doesn't FIX BUGS.









On Feb 23, 7:07 am, "dhbernard" <dhbern...@gmail.com>wrote:



-

and I make a great living using VB6.



I won't use .NET until it stops crashing; it's on everyones' desktop

(if they can't push it down for antitrust concerns then break up the

company and move on)

and I won't use .NET until it fully supports impoting from VBA and VBS

and probably even backporting .NET code back into Vb6.



it should be a two-way trip.



MAYBE once they market a complete solution is when I give them

PERMISSION to kill Vb6







On Feb 23, 7:07 am, "dhbernard" <dhbern...@gmail.com>wrote:



-

support.microsoft.com/kb/318785">support.microsoft.com/kb/318785



Take a look at the VB code here, which works for service packs within

1.0 and 1.1:

addressof.com/blog/archive/2004/09/21/926.aspx">addressof.com/blog/archive/2004/09/21/926.aspx



I was easily able to extend this to seaching for framework 2.0 by

defining 2.0's registry key name as "SOFTWARE\Microsoft\NET Framework

Setup\NDP\v2.0.50727"



Within a try block, try

key = Registry.LocalMachine.OpenSubKey("SOFTWARE\Microsoft\NET

Framework Setup\NDP\v2.0.50727", false)



Your machine to installed framework relationship may be 1:N, not 1:1.

There may very well be runtime effects that occur because of this,

which would be a valid complaint. I would be interested in learning

about and discussing such cases. But that doesn't seem to be the meat

of your complaint. What doesn't work here? Please, explain why this

doesn't work because I think it's pretty neat.



Between retrieving the SP registry value at registry settings location

for each version of the framework, or retrieving the Version file

property of Mscorlib.dll within each framework directory under

%systemroot%\Microsoft.NET\Framework, I don't understand what is

wrong.





-

"kgerritsen" <kig25@drexel.edu>wrote in message

He's trolling -- just trying to cause trouble.

Robin S.





-

a) THAT KB ARTICLE DOES NOT WORK ON WINDOWS 98 RIGHT?

b) THAT KB ARTICLE DOES NOT WORK ON WINDOWS 98 RIGHT?

c) THAT KB ARTICLE DOES NOT WORK ON WINDOWS 98 RIGHT?





On Feb 23, 1:11 pm, "kgerritsen" <k...@drexel.edu>wrote:



-

so you have a VBS file that can run, without any .NET installed in

order to tell me 'which version of the framework is the default

version'?



and it will run on Windows 95, 98, 2000, ME, NT, XP, 2003 and Vista?



NOW ALL YOU NEED TO DO IS SEND THAT VBS TO GET THEM TO INCLUDE IT IN

WINDOWS!!!!!!!!



so the scenario #1 is this:



a) Johnnie calls me up and says that he can't get Susie 4.2 to run on

my new Dell

b) Susie replies 'ok johnnie, now just open up the registry'



BAM Susie gets shit-canned for having an end user muck around in the

registry



scenario #2 is this:

a) Johnnie calls me up and says that he can't get Susie 4.2 to run on

my new Dell

b) Susie says 'oh i will email you this VBS file to your hotmail

account'

c) VBS GETS STRIPPED, right?



scenario #3 is this:

a) Johnnie calls me up and says that he can't get Susie 4.2 to run on

my new Dell

b) Susie says 'oh look in the C:\Windows\Framwork\Sucks path

c) Johnnie does; but wait a second, Johnnie never told anyone that

this was on a virtual machine or a dual boot and the C drive isn't the

C drive ROFL



scenario #4 is this:

a) Johnnie calls me up and says that he can't get Susie 4.2 to run on

my new Dell

b) Susie replies 'what the fuck is wrong with you, nobody runs the

framework on the desktop'



scenario #5 is this:

a) Johnnie calls me up and says that he can't get Susie 4.2 to run on

my new Dell

b) Susie instructs Johnnie to install framework 2.0 when it really

needs 1.1

c) brand spaking new Nimda.NET comes out and because Johnnie installed

something -- OUT OF SCOPE-- johnnies machine is flattened; the Chinese

break into a sensitve military network and invade Japan, Taiwan and

Korea without any response from the US-- because they brought down our

computers first



so which is it?



do I need to continue?

scenario #6 is this:

a) Johnnie calls me up and says that he can't get Susie 4.2 to run on

my new Dell

b) Susie says 'you don't have 4 terabytes of ram, you can't run the

VB.net apps on your DESKTOP



scenario #7 is this:

a) Johnnie calls me up and says that he can't get Susie 4.2 to run on

my new Dell

b) Susie says 'oh don't worry about I just rewrote it as VB6 because

I'm sick and tired of all of the support telephone calls.. and Vb6

works on every version of Windows out of the box!



#7 = ONE HAPPY CUSTOMER



On Feb 23, 1:11 pm, "kgerritsen" <k...@drexel.edu>wrote:



-