Author Topic: Platinum Blockland version 4.01  (Read 14953 times)

Could I test for Vista?

make it for mac.
When I have the chance I may have it rewritten for Macintosh.

I'll beta-test for Ubuntu.
We dont have a beta testing "slot" for Ubuntu, sorry.

Could I test for Vista?
I already have a tester for Vista, you wont mind being a backup, do you?

Like yours.
His what?
You're not reffering to blockland cloud, are you?
Because that's not third party, it's ingame.

His what?
You're not reffering to blockland cloud, are you?
Because that's not third party, it's ingame.
I am sure we can forget about Blockland Cloud. It will never be done, like it hasn't already been abandoned already.

For WinServ, will testers only have to test "server-related" features or all of them.
Offtopic: Where in VS did you generate the interop library?
« Last Edit: March 13, 2011, 02:48:38 PM by DontCare4Free »

For WinServ, will testers only have to test "server-related" features or all of them.
Offtopic: Where in VS did you generate the interop library?
Why not just test the entire application?
Add Reference?

Why not just test the entire application?
Because of some graphics driver issue related to XenServer which causes Blockland to refuse to start except for in dedi-mode. Not sure if that affects anything though.
Add Reference?
I can't find it in there. I tried just adding a reference to %windir%\System32\Shell32.dll but nothing happens when I click add.

Because of some graphics driver issue related to XenServer which causes Blockland to refuse to start except for in dedi-mode. Not sure if that affects anything though.I can't find it in there. I tried just adding a reference to %windir%\System32\Shell32.dll but nothing happens when I click add.
When you add the reference, you get the Shell32.dll commands (im pretty sure you know that).
You get the Interop.Shell32.dll in your bin/release or bin/Debug or obj/release or bin/Debug folder.
The interop dlls have to be in the same location as the application or your application will crash upon launching.

When you add the reference, you get the Shell32.dll commands (im pretty sure you know that).
You get the Interop.Shell32.dll in your bin/release or bin/Debug or obj/release or bin/Debug folder.
The interop dlls have to be in the same location as the application or your application will crash upon launching.
I do realize that, the thing is that I can't find how to ADD the reference. When I click add, it doesn't change to remove like it should and the reference list is not updated.

That UI looks like the inside of satans starfish.

I do realize that, the thing is that I can't find how to ADD the reference. When I click add, it doesn't change to remove like it should and the reference list is not updated.
Have you tried show all and looking under the reference list? You kind of got me confused.

That UI looks like the inside of satans starfish.
Shiny.

Have you tried show all and looking under the reference list? You kind of got me confused.
Tried that, still not working.
What version are you using?
EDIT: Seems like it was caused by an add-in (Productivity Power Tools).
« Last Edit: March 13, 2011, 03:21:19 PM by DontCare4Free »

Tried that, still not working.
What version are you using?
EDIT: Seems like it was caused by an add-in (Productivity Power Tools).
VB 2008 Express. VB 2010 was just horrible.

VB 2008 Express. VB 2010 was just horrible.
I'm using VS2010 (a paid edition).
What was so horrible about 2010?

I'm using VS2010 (a paid edition).
What was so horrible about 2010?
The controls (such as editing preferences) did not work, resizing forms, and drag and drop. These would happen on a daily basis.