Re: How to make the app run?????

ok, I'm slowely catching some of the pieces here.

There's no way I'm going to travel 60 km to test every step, some errors was
discovered on anoter machine of me, so I'll have to assume whats going wrong
when at customer.

There is a try..catch when opening the connection that can explain that
problem.
I'm still surprised that the attempt to retrieve info from the db is not
throwing an error if the connection never was opened, I've no try....catch
doing that.

btw, How can i tell if i'm using ADO as in VB or .Net ADO ??


Kjell


"Norman Yuan" wrote:

Do you have any try{...}catch(...){...} block in your code? if yes, place
MessageBox.Show() in the catch... clause so any error caught would pops up a
message box.

You can also place some message boxes before and after problemetic code
(some that "skipped". BTW, no code would simply skip by its own). For
example, you could place code to open connection (I hope you use ADO.NET,
not ADO as in VB) under a button click event handler, you may place a few
message boxes in every few lines of code. So, the clicking on button would
either open the connecction successfully, or failed with runtime error
raised. By seeing the message boxes pop up one by one, you would have idea
if your code runs to its end.


"Kjell" <Kjell@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1061FECB-ED88-4089-8E82-8FA763D9BEB3@xxxxxxxxxxxxxxxx
ok.

First of all, it was not shown to my customer, I took it to a very nice
customer letting me use his network for testings.

It's a MDI app with three child forms and a couple of dialogs, It's not a
"ready" app. it's more of a cross section of a typical "My app" "lowest
level" just to confirm best practice. (I'm moving from VB6 towards C#)

so, I wanted to check that certain things is running as I was hoping.
and yes; I've made an Installation package.

so the execution looked first ok, the MDI form came up, what I did not see
is that the call to open the ADO connection to a locally stored Access DB
was
kind of "skipped"

I don't know any other word for it, let me list which part I manage to
verify that never got executed.

I think this is equvilent to VB GetSettings
this.Left = (int)Application.UserAppDataRegistry.GetValue(this.Name +
"left", 50);
anyway, it was skipped.

''this is a nice function I found
User MyU = new User();
MyU.InitializeWithWindowsUser();

if (MyU.IsInRole("Domänadministratörer"))
mess = "You are a Domänadministratörer";
MessageBox.Show(mess);
it was skipped

and finally, open the database.
I don't know exactly what did not get executed, it could be open an
external
file to get the Path for the database.
Or the ADO Open connection string, but I'm testing the result from the
file
reading and if it fails I try to get input from user with OpenFileDialog.
this never show up so the whole function must have been skipped.

so with no ADO connection the child forms will not show anything.

End of program

I made the program very small by purpose, to get minimum chans for bugs
and
maximum chans for a positive test run in customer environment.

Kjell

"Norman Yuan" wrote:

You need to provide more information on the "not working" thing. And it
is
very common with a not thorough testing application does not work on the
client computer.

Is your app an Window Form application? (it seems yes)

How do you get in "installed" on client computer? Did you created an
installation package? Or did you simply XCopied whole folder to the
client
computer? Dod you "install" it locally or on a network share?

Is proper version of .NET framework installed on the client computer?

With such very basic information, only thing that can be said is you did
not
do things correctly and show your app to your client a bit too early.


"Kjell" <Kjell@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:CDF17685-5F17-41CE-8F0D-9F0A35DF0006@xxxxxxxxxxxxxxxx
Hello

I've taken a four days training in C#, very good training, experienced
teacher and all that, very positive.

Went home spent a week making my first application, slightly more than
the
usual "Hello world".

Took it with me to my best customer, and beleive it or not....It will
not
work !!!!

How can that happen!!!
It works fine on my XP-pro at home and not at all on my customers
XP-pro
with all updates, with Domain User account, no matter how I try, it
refuses
to execute certain sections of the code, everything trivial like
showing a
form (empty of course) no problem, but everything interesting like open
the
ADO connection to the databas, get the recordset filled and fill the
List
on
the empty form NOPE, can't do that due to some .Net Framework security
issues.

So, How can I make 200 client machines accept my C# code without
manually
configuring them one by one?

Kjell






.