«

ASP.net doesn't support the WORLDS MOST POPULAR LANGAUGE

STICK A FORK IN IT KID, MOVE BACK TO A PRACTICAL LANGUAGE





On Feb 14, 5:15 am, "Mr. Arnold" <"Mr. Arnold"@Arnold.COM> wrote:
> BoogieWithSt...@gmail.com wrote:
>
> > The computers in question are using IE6 on XP Pro SP2. I use IE6 on
> > XP PRO SP2 here at work and everything is fine. I have also tried on
> > other computers using IE6, IE7, Firefox 1.x and 2.0 with no problems.
> > It is only IE6 on some machines. The processes for the account lookup
> > and the product lookup are identical except for the different tables
> > and fields.
>
> The bottom line is there is something different about those machines
> you're having problems with. You need to find out what the difference is
> and address the problem.

RE:

Again, you don't know what you're talking about when it comes to .NET.
I
have been using VB.NET and have used VB 6 for many years. I don't have
a
problem using VB.NET. It has done everything I have asked it to do
and
more programming wise. And so has C# .NET done everything and more I
have asked it to do programming wise.




WHAT ABOUT VBS, VBA AND SQL SERVER JOBS?
WHAT ABOUT VBS, VBA AND SQL SERVER JOBS?
WHAT ABOUT VBS, VBA AND SQL SERVER JOBS?
WHAT ABOUT VBS, VBA AND SQL SERVER JOBS?
WHAT ABOUT VBS, VBA AND SQL SERVER JOBS?


because that is 40% of my workload; the rest is writing SQL.
AND I RECCOMEND THAT EVERYONE LEAVES THE MS CAMP BECAUSE THEY BETRAYED
US FOR THE MOTHER ****ING LAST TIME

ROFL







On Feb 14, 2:54 am, "Mr. Arnold" <"Mr. Arnold"@Arnold.COM> wrote:
> pfc_s...@hotmail.com wrote:
> > UNNECESSARY CHANGE IS NOT SEXY
> > UNNECESSARY CHANGE IS NOT NECESSARY
>
> > UNTIL MS BRINGS BACK CLIENTSIDE VBSCRIPT IN ASP.NET I WILL NOT LAY
> > DOWN AND SURRENDER
>
> You can use VBScript, JavaScript and ECMAScript in ASP.NET solution on
> the client or server side.
>
> You can even use pure JavaScript with the ASP.NET code behind file that
> has no Web form or Web controls, eliminating the Post Back even period,
> with Ajax Pro for .NET. The .NET Code Behind file is only used to
> provide proxies for utilities such access to databases, etc, etc.
>
> http://www.codeplex.com/AjaxPro
>
>
>
> > UNNECESSARY CHANGE IS NOT SEXY
> > UNNECESSARY CHANGE IS NOT NECESSARY
>
> You don't know what you're talking about when it comes to .NET.
>
>
>
> > dotnet doesn't work in 1/4 of the places that VB6 works.
>
> Again, you don't know what you're talking about when it comes to .NET. I
> have been using VB.NET and have used VB 6 for many years. I don't have a
> problem using VB.NET. It has done everything I have asked it to do and
> more programming wise. And so has C# .NET done everything and more I
> have asked it to do programming wise.
>
>
>
> > it is a 25% solution at best.
>
> > Does it make sense for programmers to go from ONE LANGUAGE TO FOUR?
>
> > STICK A ****ING CORK IN IT DIPSHIT
>
> You don't know what you're talking about when it comes to .NET.
>
>
>
> > there's a hundred kids in China, willing to work for 1/100th of what
> > you do.. and they have free web servers; an IDE that doesn't go
> > 'visual fred' every 18 months and free database servers
>
> They can do whatever they want there in that country. It doesn't hold
> water here in the US.
>
> And again, you don't know what you're talking about when it comes to .NET
>
>
>
> > eat a dick whore
>
> > DOTNET IS A FAILURE, MOVE BACK TO VB6
>
> I would say that the rest of the software language developers would
> disagree with you.
>
> http://www.dotnetpowered.com/languages.aspx
>
> .Net is a standard that is owned by the ISO and ECMA. MS doesn't own
> .NET. MS owns VB.NET which is proprietary to MS. MS gave .NET away so
> that it could ratified as a *standard* to be used by anyone who has
> contacted the ISO and ECMA to use the common .Net Framework CLI/CLR
> which is common to all .NET languages.
>
> MS doesn't own C# .NET either which has been ratified as standard owned
> and controlled by the ISO and ECMA. C++ will be next to be ratified as a
> standard owned and controlled by the ISO and ECMA
>
> http://en.wikipedia.org/wiki/.NET_Fr...tion_and_Licen...
>
> I like your lip service that won't hold water. .NET is not going
> anywhere and it will be used regardless of you like it or not.
>
> It's plain and simple. You're out of touch with reality and out of your
> mind.

please provide title and page number of said books

> Dear Mr Arnold:
>
> RE:
> You can use VBScript, JavaScript and ECMAScript in ASP.NET solution
> on
> the client or server side.
> I WOULD LIKE TO SEE THIS IN WRITING FROM MICROSOFT.
>
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> PERMITTED IN ASP.NET
> On Feb 14, 2:54 am, "Mr. Arnold" <"Mr. Arnold"@Arnold.COM> wrote:
>
>> pfc_s...@hotmail.com wrote:
>>
>>> UNNECESSARY CHANGE IS NOT SEXY
>>> UNNECESSARY CHANGE IS NOT NECESSARY
>>> UNTIL MS BRINGS BACK CLIENTSIDE VBSCRIPT IN ASP.NET I WILL NOT LAY
>>> DOWN AND SURRENDER
>>>
>> You can use VBScript, JavaScript and ECMAScript in ASP.NET solution
>> on the client or server side.
>>
>> You can even use pure JavaScript with the ASP.NET code behind file
>> that has no Web form or Web controls, eliminating the Post Back even
>> period, with Ajax Pro for .NET. The .NET Code Behind file is only
>> used to provide proxies for utilities such access to databases, etc,
>> etc.
>>
>> http://www.codeplex.com/AjaxPro
>>
>>> UNNECESSARY CHANGE IS NOT SEXY
>>> UNNECESSARY CHANGE IS NOT NECESSARY
>> You don't know what you're talking about when it comes to .NET.
>>
>>> dotnet doesn't work in 1/4 of the places that VB6 works.
>>>
>> Again, you don't know what you're talking about when it comes to
>> .NET. I have been using VB.NET and have used VB 6 for many years. I
>> don't have a problem using VB.NET. It has done everything I have
>> asked it to do and more programming wise. And so has C# .NET done
>> everything and more I have asked it to do programming wise.
>>
>>> it is a 25% solution at best.
>>>
>>> Does it make sense for programmers to go from ONE LANGUAGE TO FOUR?
>>>
>>> STICK A ****ING CORK IN IT DIPSHIT
>>>
>> You don't know what you're talking about when it comes to .NET.
>>
>>> there's a hundred kids in China, willing to work for 1/100th of what
>>> you do.. and they have free web servers; an IDE that doesn't go
>>> 'visual fred' every 18 months and free database servers
>>>
>> They can do whatever they want there in that country. It doesn't hold
>> water here in the US.
>>
>> And again, you don't know what you're talking about when it comes to
>> .NET
>>
>>> eat a dick whore
>>>
>>> DOTNET IS A FAILURE, MOVE BACK TO VB6
>>>
>> I would say that the rest of the software language developers would
>> disagree with you.
>>
>> http://www.dotnetpowered.com/languages.aspx
>>
>> .Net is a standard that is owned by the ISO and ECMA. MS doesn't own
>> .NET. MS owns VB.NET which is proprietary to MS. MS gave .NET away so
>> that it could ratified as a *standard* to be used by anyone who has
>> contacted the ISO and ECMA to use the common .Net Framework CLI/CLR
>> which is common to all .NET languages.
>>
>> MS doesn't own C# .NET either which has been ratified as standard
>> owned and controlled by the ISO and ECMA. C++ will be next to be
>> ratified as a standard owned and controlled by the ISO and ECMA
>>
>> http://en.wikipedia.org/wiki/.NET_Fr...tion_and_Licen
>> ...
>>
>> I like your lip service that won't hold water. .NET is not going
>> anywhere and it will be used regardless of you like it or not.
>>
>> It's plain and simple. You're out of touch with reality and out of
>> your mind.
>>

Jay Parzych wrote:
> please provide title and page number of said books
>
>> Dear Mr Arnold:
>>
>> RE:
>> You can use VBScript, JavaScript and ECMAScript in ASP.NET solution
>> on
>> the client or server side.
>> I WOULD LIKE TO SEE THIS IN WRITING FROM MICROSOFT.

http://msdn2.microsoft.com/en-us/library/aa479302.aspx

I am only the messenger.

Larry Linson wrote:
> Dear Mr Arnold:
>
> RE:
> You can use VBScript, JavaScript and ECMAScript in ASP.NET solution
> on
> the client or server side.

Here you go little one.

http://msdn2.microsoft.com/en-us/library/aa479302.aspx

I am just the messenger.

I am pretty darn sure it is in 'Web Database Development Step by
Step .NET edition'

I can't find it right now though and tonights Valentine's
I will look it up tomorrow I'm heading out for a meeting 2 hours away

if this book was just flat out wrong-- that would be great.
this is the single reason I've refused to consider ASP.net for
_ANYTHING_

I mean seriously here. I've been writing BASIC since the Commodore 64
and I will never ever ever consider any Java or JavaScript or C# or C+
+ or C of C# or JScript solution.

I REFUSE TO USE THEM; VB WAS THE WORLDS MOST POPULAR LANGUAGE CIRCA
1998-2002

(well that and the fact that Office Web Components has no replacement
in ASP.net ROFL)

I will definitely find the reference and get it to you... I'm thikning
it was a book geared towards VB people and it specifically said that
clientside vbScript does not work in ASP.net.

The funny thing is; I could have sworn it was an orange book; not the
black covers.. I just don't see any orange ASP.net books on my shelf..
I will find it and produce

If the book is WRONG I fully expect MS to send me a new copy of the
book.

and if the book is RIGHT (which I believe it is-- since I tried to get
it workign for a month back in '03 and I couldn't get anywhere; and I
emailed a whole ton of people at MS about it any nobody could tell me
a way to get it working)

of course; they fired me for bitching about VB and SQL Server; I
mean.. they con us into .NET instead of fixing SQL authentication?
ROFL how does this company get away with this crap?

so it's not like anything MS says or does (except bring back VB com,
and / or make VB.net a complete replacement; including OFFICE VBA, SQL
JOBS, VBS FILES AND _CLIENTSIDE DHTML PROGRAMMING_)

trust me; I will find the reference for sure






On Feb 14, 9:28 am, Jay Parzych <jimp...@cox.net> wrote:
> please provide title and page number of said books
>
>
>
> > Dear Mr Arnold:
>
> > RE:
> > You can use VBScript, JavaScript and ECMAScript in ASP.NET solution
> > on
> > the client or server side.
> > I WOULD LIKE TO SEE THIS IN WRITING FROM MICROSOFT.
>
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > I HAVE BOOKS FROM MS PRESS THAT SAID THAT CLIENTSIDE VBSCRIPT IS NOT
> > PERMITTED IN ASP.NET
> > On Feb 14, 2:54 am, "Mr. Arnold" <"Mr. Arnold"@Arnold.COM> wrote:
>
> >> pfc_s...@hotmail.com wrote:
>
> >>> UNNECESSARY CHANGE IS NOT SEXY
> >>> UNNECESSARY CHANGE IS NOT NECESSARY
> >>> UNTIL MS BRINGS BACK CLIENTSIDE VBSCRIPT IN ASP.NET I WILL NOT LAY
> >>> DOWN AND SURRENDER
>
> >> You can use VBScript, JavaScript and ECMAScript in ASP.NET solution
> >> on the client or server side.
>
> >> You can even use pure JavaScript with the ASP.NET code behind file
> >> that has no Web form or Web controls, eliminating the Post Back even
> >> period, with Ajax Pro for .NET. The .NET Code Behind file is only
> >> used to provide proxies for utilities such access to databases, etc,
> >> etc.
>
> >>http://www.codeplex.com/AjaxPro
>
> >>> UNNECESSARY CHANGE IS NOT SEXY
> >>> UNNECESSARY CHANGE IS NOT NECESSARY
> >> You don't know what you're talking about when it comes to .NET.
>
> >>> dotnet doesn't work in 1/4 of the places that VB6 works.
>
> >> Again, you don't know what you're talking about when it comes to
> >> .NET. I have been using VB.NET and have used VB 6 for many years. I
> >> don't have a problem using VB.NET. It has done everything I have
> >> asked it to do and more programming wise. And so has C# .NET done
> >> everything and more I have asked it to do programming wise.
>
> >>> it is a 25% solution at best.
>
> >>> Does it make sense for programmers to go from ONE LANGUAGE TO FOUR?
>
> >>> STICK A ****ING CORK IN IT DIPSHIT
>
> >> You don't know what you're talking about when it comes to .NET.
>
> >>> there's a hundred kids in China, willing to work for 1/100th of what
> >>> you do.. and they have free web servers; an IDE that doesn't go
> >>> 'visual fred' every 18 months and free database servers
>
> >> They can do whatever they want there in that country. It doesn't hold
> >> water here in the US.
>
> >> And again, you don't know what you're talking about when it comes to
> >> .NET
>
> >>> eat a dick whore
>
> >>> DOTNET IS A FAILURE, MOVE BACK TO VB6
>
> >> I would say that the rest of the software language developers would
> >> disagree with you.
>
> >>http://www.dotnetpowered.com/languages.aspx
>
> >> .Net is a standard that is owned by the ISO and ECMA. MS doesn't own
> >> .NET. MS owns VB.NET which is proprietary to MS. MS gave .NET away so
> >> that it could ratified as a *standard* to be used by anyone who has
> >> contacted the ISO and ECMA to use the common .Net Framework CLI/CLR
> >> which is common to all .NET languages.
>
> >> MS doesn't own C# .NET either which has been ratified as standard
> >> owned and controlled by the ISO and ECMA. C++ will be next to be
> >> ratified as a standard owned and controlled by the ISO and ECMA
>
> >>http://en.wikipedia.org/wiki/.NET_Fr...tion_and_Licen
> >> ...
>
> >> I like your lip service that won't hold water. .NET is not going
> >> anywhere and it will be used regardless of you like it or not.
>
> >> It's plain and simple. You're out of touch with reality and out of
> >> your mind.- Hide quoted text -
>
> - Show quoted text -

Larry Linson wrote:
> and I don't know what I'm talking about?
>
> WHY DOES VBA STILL LIVE IN OFFICE?

Who cares about VBA being used in Office, when you can use .NET to
access office solutions?

http://support.microsoft.com/default.aspx/kb/311452

> WHY CANT I USE DOTNET IN VBS?

I would suspect that you have no *clue* on how to do it.

http://www.codeproject.com/dotnet/nettocom.asp

> WHY CANT I USE DOTNET IN ACTIVEX SCRIPTS IN SQL SERVER JOBS?
>
>

Who cares about *you* not being able to use ActiveX scripts in SQL Server?

Maybe, it's because you have no *clue* and what .NET language to use.

http://support.microsoft.com/default.aspx/kb/232394

You should turn in your .NET badge.

Larry Linson wrote:
> ASP.net doesn't support the WORLDS MOST POPULAR LANGAUGE
>
> STICK A FORK IN IT KID, MOVE BACK TO A PRACTICAL LANGUAGE

It's your opinion and it's a dime a dozen and I would say pretty much
worthless.

Larry silly clown and big mouth Linson wrote:

<snipped>

I am not even going to bother here. You are a *clown* beyond *clowns*.

<g>

Jay Parzych wrote:
> please provide title and page number of said books
>
>> Dear Mr Arnold:
>>
>> RE:
>> You can use VBScript, JavaScript and ECMAScript in ASP.NET solution
>> on
>> the client or server side.
>> I WOULD LIKE TO SEE THIS IN WRITING FROM MICROSOFT.

http://www.codeplex.com/AjaxPro
http://msdn2.microsoft.com/en-us/lib...2a(VS.80).aspx

I am just the messenger.

And the boy is talking MS Press books that only give you a foundation to
start with and nothing else. The boy couldn't change gears if the gear
hit him in his big mouth.