Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Major mixup in two ASP.NET transactions
Message
From
04/09/2006 11:59:20
 
 
General information
Forum:
ASP.NET
Category:
Other
Environment versions
Environment:
VB 8.0
OS:
Windows XP SP2
Database:
Visual FoxPro
Miscellaneous
Thread ID:
01150471
Message ID:
01150721
Views:
45
>That code is fine - you're creating a new Framework object for every hit. But then you said that, to avoid the initialisation overhead you wanted to use:
>
>  oApp=LXFramework
>
>where LXFramework was the global framework object. That's where you'd have the problem.

Ok, that is what I thought when reading your message after. Ok, for sure, I have something safe as it is now.

To enhance that, in order to avoid doing the framework initialization every time, I was thinking of using a copy of the application framework object. But, as you said, doing it as I first thought wouldn't work. My question is is there a way in .NET to take a copy of an object or we can only have references to them? Lets say basically that I would have a customer object. In my code, I would want to have four identical copies of the customer objects so I can have them in the code in the same method to apply specific business logic. Would it there be a way in .NET to obtain four copies instead of references?
Michel Fournier
Level Extreme Inc.
Designer, architect, owner of the Level Extreme Platform
Subscribe to the site at https://www.levelextreme.com/Home/DataEntry?Activator=55&NoStore=303
Subscription benefits https://www.levelextreme.com/Home/ViewPage?Activator=7&ID=52
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform