Architect

You can still build executable programs with VSNET2003 trial cd, after it's 60 day license has expired.
Enter this non-trademarkable, non-copyrightable(base 36) number.

D64GG-GXY6T-V6FTR-WCPBB-2YDYB

It will accept this number
Upon loading it will say "invalid key etc".
Do not click ok.
Click on the IDE, and it will be brought to front.
You are entitled to use the IDE, as it says.
Though some features are non-functional.
There are easy workarounds for most of these missing features. To save your project have to close out the ide.
You also have to make a new properties window, or have one previously made/saved. Although if you build your own entire VS.YOU, then Im sure MS wants you, and you dont need to go this lengthy route.












I AM THE ARCHITECT, I CREATED THE MATRIX.

Talking about such things is against forum rules, I would suggest editing your post and removing the content, before a moderator takes notice.

Also, if your going to pirate anything... pirate the full version. :p

As Bugs Bunny would say "What a maroon!"

This is not against any implied rules, anyone is legally free to use this part of the software, if you have an official 2003 trial CD.

It says right in the IDE, that you are not entitled to certain parts of the program, and they are rendered useless.
By implicit default, this means you are entitled to what is still available(enabled). I know I am right on this.


Who is the fool here bugs?

If the "60 day license has expired" that means that YOU are NOT permitted to use the software even if you STILL CAN.

Did you read the licence aggreement before you intalled?

No, the agreement applies to THE full product.("""software""")

It says exactly:
Save: "This command not available until you renew your license."

Other commands are available without a renewal of your license.
The creators intended this, otherwise it would say it directly.
You may not use any commands under the license agreement etc.

I hope that makes a little more sense.:wave:
BTW, i noticed your avatar so i figured I'd sing ya korn song.

You not em pap en radat eh dodepoo, try to take it, no not where were at, ta take em batriadat down to shapenta, ehraa sa pen breet cha think about bat erhaah! subjecting me, to that memorating party, mm take ma, i want to take me mo ride in bruruah after I listen huh, hey my hair dog, aint no ro rat.

twist twist twist.

I actually found that when rebuilding the same exact project, with the same PC, and Os that the semi-disabled build catches errors that are not caught with the full product installed.
I had a double If, end if statement problem.
During debugging(full) sometimes the flow was going through the wrong If,end if, since I had given it the same conditions, under multiple avenues. The result was sporatic behaviour, where the code near the area was affected. I could not figure out why, since it was building fine. The eventual fix was a sub procedure.

I strongly recommend using this as a final method before releasing executables. You can actually do just about anything by working around all the convinent features(buggy) included with the full product, though things are as bit slower to adjust to.

In fact, I am much more willing to buy the product, seeing it from this dual standpoint. It gives you a chance to apprieciate the convinience of it all!!

Does the upgrade version from VB6 enterprise to VBNET2003, need the original cd?
Or will it upgrade from an installed VB6 enterprise?

:ehh: