|
Thanks , But
This win app is on network and several users can run this app simultaneously , doesn't it cause any problem?
|
|
|
|
|
Sorry for taking so long to get back to you. Anyway, here's the answer.
DotNetWWW wrote: Thanks , But
This win app is on network and several users can run this app simultaneously , doesn't it cause any problem?
No, because each user will have this app running in a different process space.
Deja View - the feeling that you've seen this post before.
|
|
|
|
|
Dear All,
I have created a windows installer package for my VB.NEt project. When i install it to another computer, it is displayning a message "This setup requires the .NET Framework version 1.1.4322. Please install the .NET Framework and run this setup again. The .NET Framework can be obtained from the web. Would you like to do this now?" How can i avoid this message, when i creating setup project, or How can I integrade .NET Framework with my setup project.
Can't we run .NET Setup files without installing .NET Framework?
Pls help
|
|
|
|
|
dimuthuvbnet wrote: How can i avoid this message
Install the .NET Framework 1.1 and it's service packs.
dimuthuvbnet wrote: How can I integrade .NET Framework with my setup project.
You can't bundle it into your .MSI. It has to be run as a seperate installation. That CAN be launched from an .EXE setup. Just Google for ".NET Framework BootStrap Install".
dimuthuvbnet wrote: Can't we run .NET Setup files without installing .NET Framework?
No. One of the prereq's built into the MSI is the .NET Framework must be installed.
|
|
|
|
|
dimuthuvbnet wrote:
Can't we run .NET Setup files without installing .NET Framework?
Nope, it is a requirement.
"Find it your bloody self - immediately!" - Dave Kreskowiak
|
|
|
|
|
hello everyone
im currently learning c# and i recently discovered some strange behaviour in the .NET framework 2.0 (using VS2005 Pro). i wrote my own textbox which does, along with other things, change the Borderstyle on the leave event. but it doesnt work, the below code has the effect that when using the mouse to leave the textbox everything works, but with TAB, youre trapped in the box. changing any other property instead of borderstyle is not a problem. only with this very property it acts weird.
anybody had this before? is this a bug or did i miss something?
thanks for reading and maybe answering this!
public class TextBoxTest : TextBox
{
protected override void OnLeave (EventArgs e)
{
BorderStyle = Borderstyle.Fixed3D;
base.OnLeave (e);
}
}
PS: first post here, so please be nice if i did something wrong 
|
|
|
|
|
Okay guys, just found this one on the microsoft feedback page:
http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=185568
seems like this one is not solvable atm 
thx for reading though
|
|
|
|
|
We are having problems correctly managing our configuration files across multiple servers and environments. Currently we either save a separate copies of the configuration files for each environment or comment out values for other environments and add the new environments values beneath. There has to be a better way!!!
Does anyone know of an application that will manage these configuration files? Something that preferably will also version control the configuration files?
|
|
|
|
|
We use sourcecontrol for the different config files. We maintain a version for each environment, e.g DEV, UAT, TEST, PROD, and as part of our automated deployment process, we pick up the appropriate config file. It's relatively easy to do as long as you can script your particular source control system.
Deja View - the feeling that you've seen this post before.
|
|
|
|
|
Hi,
In my system, i have .net 2.0 installed. But i have to work(modify) on a project which was created in .net 1.1. My question is will it create some technical issues while building.
Please suggest me a solution...... its urgent
Bala 
|
|
|
|
|
Yeah, you can't do it.
VS 2005 will compile against the .NET Framework 2.0 only. You'll have to open the project in VS.NET 2003 for it to compile against .NET 1.1.
|
|
|
|
|
If you have .NET 1.1 installed, you'll need to compile it up from the command line. Use csc.exe with relevant options to do this. Note that you'll have to put the path into the csc for the .net 1 framework so that you don't launch the .Net 2 compiler by accident.
Deja View - the feeling that you've seen this post before.
|
|
|
|
|
Now there you went and told him how to do it the "easy" way. You fountain of wisdom you. 
|
|
|
|
|
Dave Kreskowiak wrote: you went and told him how to do it the "easy" way
That's me. Always looking for the shortcut.
Deja View - the feeling that you've seen this post before.
|
|
|
|
|
HI All,
Thanks a Lot for All who helped out. Ill use VS2003 with Framework 1.1.
Regards,
Bala
|
|
|
|
|
Bala J wrote: its urgent
That is rather rude to say.
Bala J wrote: i have .net 2.0 installed. But i have to work(modify) on a project which was created in .net 1.1. My question is will it create some technical issues while building.
There shouldn't be too much of an issue. You'll have to run the 1.1 code through the code converter on VS 2005 and take it from there. Convert it to 2.0 and forget about 1.1...
"Find it your bloody self - immediately!" - Dave Kreskowiak
|
|
|
|
|
You can install both versions at the same time.. with out any issue.
|
|
|
|
|
Hi,
Can someone help me out.
I have 2 controls A and B on the same parent and both dock = fill, when i set A to background and the B to foreground.
The foregrond control B has enabled = false.
When i click with my mouse on control B, the background control has been triggered. When a button is on the control A it's also triggered, even when i don't see it.
What happens here? A huge .net bug ?
Thx for you're help.
Kurt
|
|
|
|
|
topcatalpha wrote: What happens here? A huge .net bug ?
No. A disabled control doesn't get the mouse message. It's going to the topmost control that's still enabled.
|
|
|
|
|
Seems pretty dangerous to me.. clicking on something you can't see...
i cannot see a good reasons to implement such thing, so i guess it's a shortcomming in dotnet or so..
how to work around this? settings everything disabled?
i really need usercontrols to be created before switching to keep up the speed when changing screens.
thx for the response.
Kurt
|
|
|
|
|
Normally, noone overlays a disabled control over the top of a bunch of other controls either.
topcatalpha wrote: settings everything disabled?
Yep.
topcatalpha wrote: i really need usercontrols to be created before switching
Switching what??
topcatalpha wrote: to keep up the speed when changing screens
The more controls you have, the slow repaint is going to be. Period - end of story. There's nothing you can do about that, other than limiting the number of controls on a form.
|
|
|
|
|
hi,
thx for the respond.
Dave Kreskowiak wrote: Switching what??
switching between screens was what i ment here.
i need to switch quickly between screen and creating them is extreemly slow. You can see al controls being build and shown seperatally.
As there is no such thing as a notebook (tabcontrol without the buttonss) in dotnet i create them and bring them to front and set visible when i need them to see.
Indeed more resource for starting up, but fast when switching if you do a .refresh after bringtofront.
For my users there's no waiting and seeing the screen being build also when a lot of controls are placed on the usercontrol.
Unless i'm totally wrong here in the way i work. Then please suggest an option to prevent the slow screen builds in dotnet.
So why i disable the top control? I have a treeview at the left side of the screen and depending on the selected item in the treeview the user can or cannot edit the main screen/usercontrol that is on top.
Thx again
Kurt
|
|
|
|
|
It sounds like you're trying to put your entire app on one form, which is not a good idea. If you do any data binding of controls, you'll find that becomes a headache in an environment like this.
If this is true and you are putting every on a single form, you've increased the time is takes to create that form. There's nothing you can do about it. Creating a control is a very expensive process. Multiple that by a couple of hundred times and it takes forever.
Also, I see no reason to use UserControls. It's probably the second most abused class next to a PictureBox control. UserControl is designed to make it easier to make "composite" controls. Say a TextBox and a Button combine to make something like a Browse control. You can either type a path in the TextBox or click the Button to browser for a filepath.
Did you know that the Form class derives from Control?? Yes, you can treat a Form just like any other control, like a TextBox or Button. Design each "page" of your notebook as a seperate form, setting the FormBorderStyle to None to get rid of the title bar. Then you from your TreeView you can create and destroy each form and place it in the right side of your screen just like placing a control. When you click a new item in the TreeView, Dispose the last form created and create a new one. Just remember to set the Form's TopLevel property to False before you add it to a container controls collection.
|
|
|
|
|
Dave Kreskowiak wrote: It sounds like you're trying to put your entire app on one form, which is not a good idea. If you do any data binding of controls, you'll find that becomes a headache in an environment like this.
You're right there, not for my usercontrols, but i had this problem with databindings for controls on tabpages. Seems controls are not created the first time, after showing the tabpage the binding remains...
Dave Kreskowiak wrote: If this is true and you are putting every on a single form, you've increased the time is takes to create that form. There's nothing you can do about it. Creating a control is a very expensive process. Multiple that by a couple of hundred times and it takes forever.
I use a mainform and usercontrols in a splitpanel. it takes indeed more time to startup the app (about 2 seconds including DB connection), therefore i have a splash/login screen. but after creating it remains very fast, i don't have to create them each time.
i guess this is a choice, fast startup and slow switching or slow startup and fast switching between screens.
Dave Kreskowiak wrote: Also, I see no reason to use UserControls. It's probably the second most abused class next to a PictureBox control. UserControl is designed to make it easier to make "composite" controls. Say a TextBox and a Button combine to make something like a Browse control. You can either type a path in the TextBox or click the Button to browser for a filepath.
I use them because they can be placed on controls and are reusable. In delphi i could give a form a parent and the form docks on that panel, but that doesn't work in C# dotnet. forms are not dockable on a splitpanel. are am i wrong here?
Dave Kreskowiak wrote: Did you know that the Form class derives from Control?? Yes, you can treat a Form just like any other control, like a TextBox or Button. Design each "page" of your notebook as a seperate form, setting the FormBorderStyle to None to get rid of the title bar. Then you from your TreeView you can create and destroy each form and place it in the right side of your screen just like placing a control. When you click a new item in the TreeView, Dispose the last form created and create a new one. Just remember to set the Form's TopLevel property to False before you add it to a container controls collection.
Guess this is the solution to my question. 
Do you think using a form instead of a usercontrol will be faster ? or what is the advandage for using a form instead of a usercontrol?
Dave Kreskowiak wrote: Say a TextBox and a Button combine to make something like a Browse control.
Indeed in my case some buttons a grid and detailsfields no code behind it except for the inputfields.
I thought a usercontrol was the same like a frame in delphi. Place controls on it and make it availabe in the toolbar, just drag and drop it in designtime
Thx again.
Kurt
|
|
|
|
|
topcatalpha wrote: i guess this is a choice, fast startup and slow switching or slow startup and fast switching between screens.
Putting the controls for each page on a different form limits the number of controls you're creating on startup, and also limits the number of controls created each time a form is instantiated, so it's still pretty fast.
topcatalpha wrote: In delphi i could give a form a parent and the form docks on that panel, but that doesn't work in C# dotnet. forms are not dockable on a splitpanel. are am i wrong here?
Sure it does. Forms have a Dock property, just like any other control, and yes, it does work. The Dock property for a form doesn't show up in the Properties panel, but it can be set in code.
topcatalpha wrote: Do you think using a form instead of a usercontrol will be faster ? or what is the advandage for using a form instead of a usercontrol?
The UserControl is a bit lighter so it does create a little faster (milliseconds, I assure you.) The form has the advantage of maintaining its own BindingContext by default instead of inheriting the parent form's context.
You don't get to see a form in the ToolBox though like you do with a UserControl. But in an app like this, why would you want to?
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
