|
simple as that.
thanx a lot
daniel
|
|
|
|
|
Hello People ,
I whan't to ask you something i wor on a pascal editor in c# , with Stream writers and readers.But when i whan't to compile it(.PAS to .EXE) (i save it like a document.pas) VS 2005 sais :
The system cannot find the file specified;
Can anybody help me?
Or show me the other idea to do that ?
Thanks ...
nemanja
|
|
|
|
|
How do you hope to make your C# editor compile PASCAL ?
Christian Graus - Microsoft MVP - C++
Metal Musings - Rex and my new metal blog
|
|
|
|
|
Pray 
|
|
|
|
|
when creating a new project you get form1 which is your default main form...
so when you add a new form, and run your project and close form1 your application
terminates... this is because Form1 is MAIN FORM... is there anyway to change MAIN FORM to from2 since i no longer need form1!??
thank you...
It Is Not That I'm Different!
... I'm Only Making The Difference!
|
|
|
|
|
In your project you will have somewhere a method called static void Main (If you are running VS2005 it is in a class called Program which is automatically added to your project). This method runs the application and the form. You can alter this method to run a new form as the application's main form.
|
|
|
|
|
yes...
static void Main()
{
Application.EnableVisualStyles();
Application.SetCompatibleTextRenderingDefault(false);
Application.Run(new Form1());
}
ok... so, what if i don't want Fom1 anymore!??
lets say that i want to dispose Form1 and make Form2 my main form...
if i close Form1 and Form2 is not the main form then the application will exit...
all, i want to do... is a password dialog...
if password dialog = correct login details then
destroy form1 and load form2 as main form...
It Is Not That I'm Different!
... I'm Only Making The Difference!
|
|
|
|
|
ferdna wrote: ok... so, what if i don't want Fom1 anymore!??
lets say that i want to dispose Form1 and make Form2 my main form...
if i close Form1 and Form2 is not the main form then the application will exit...
all, i want to do... is a password dialog...
if password dialog = correct login details then
destroy form1 and load form2 as main form...
Well, I would put the login form as a dialog that is opened when the main form is loaded. But I guess you could also do it this way:
static void Main()
{
Application.EnableVisualStyles();
Application.SetCompatibleTextRenderingDefault(false);
LoginForm loginForm = new LoginForm();
Application.Run(loginForm);
if ()
{
MainForm mainForm = new MainForm();
Application.Run(mainForm);
}
}
|
|
|
|
|
this works... but... is the right way to do this!??
or is it a better way to do this!??
static void Main()<br />
{<br />
Application.EnableVisualStyles();<br />
Application.SetCompatibleTextRenderingDefault(false);<br />
<br />
Form1 form1 = new Form1();<br />
Application.Run(form1);<br />
<br />
Form2 form2 = new Form2();<br />
Application.Run(form2);<br />
}
It Is Not That I'm Different!
... I'm Only Making The Difference!
|
|
|
|
|
ferdna wrote: this works... but... is the right way to do this!??
or is it a better way to do this!??
Well, if form1 (and you really need to find better names than that. The readability and maintainability of code with class names like Form1 and Form2 is terrible.
Anyway, if form1 is your login form then why is there no condition to stop form2 from being loaded in the event that the login fails?
|
|
|
|
|
no need to... i just needed the logic...
i thank you so much for your time...
It Is Not That I'm Different!
... I'm Only Making The Difference!
|
|
|
|
|
Another method is to never show your "main form", but have all of your UI in secondary forms that you load and unload as you please. Have your UI forms notify your main form when they close, and when all UI forms close, have your main form close.
|
|
|
|
|
don't take me wrong or anything... but, i feel safer not creating my window until login has been clear... thats why i prefer the other method...
thanks!
It Is Not That I'm Different!
... I'm Only Making The Difference!
|
|
|
|
|
how to do this using .NET 3.0(WPF)!??
thanks!
It Is Not That I'm Different!
... I'm Only Making The Difference!
|
|
|
|
|
I don't know how to check that some registry key exists.
Exp:
RegistryKey key = Registry.CurrentUser.OpenSubKey("Software",true).CreateSubKey("Program");
key.SetValue("Key", "0");
So, if the key does not exists the program will fall.
How to fix this.
Vasildb
|
|
|
|
|
If the key doesn't exist the OpenSubKey method will return null. So assign the return value to a local variable, test whether it is a null reference and in case it's not call the CreateSubKey method on the local variable.
"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning." - Rick Cook www.troschuetz.de
|
|
|
|
|
I would like to learn about workflow programming. so what is the best resources i can use to read about it?
|
|
|
|
|
Search for Windows Workflow Foundation, it's the latest workflow framework from MS, all .NET based.
|
|
|
|
|
(Please note, this is a long reply to this posting [^], so I intended to write a whole new posting instead)
-----------------------------
I nearly finished "converting" the approx. 300.000 lines of C++ code of our flagship product "Zeta Producer [^]" (a Windows-based CMS) from MFC/C++ to C#.
Following is a short description of the things I experiences along the road. Since I'm currently in the right mood, I want to share them here with you  :
It roughly took me 10 month (having other smaller projects in parallel, though) to convert from C++ to C#.
My own coding experience is 15 years of C++ and maybe 5 years of C#. I strongly recommend that you really know both languages (and their libraries MFC and BCL!) very well.
I do think I still have a lot of (smaller) bugs due to the conversion, but we already do use Zeta Producer (version 8 now) internally in serveral projects and several beta testers do use them, too.
The "Porting"
The steps I did when "converting" (inside quotes, cause it was rather a rewrite than a conversion) where roughly:
- Re-create all MFC-present dialogs, windows, controls from scratch inside the Windows Forms designer. No functionality, just the plain GUI.
- Port all non-visual code by first creating all classes inside C#. This was the largest part. I did it by creating file by file (for each .h/.cpp pair, I did one .cs file), copying the content of one C++ class into the corresponding .cs file. Then I manually changed the syntax until no code editor errors are present any more. This really took looooooooooong, since it were several hundreds of files.
- Add the event handlers for all Windows Forms. The same way as in 2.).
- Build the first time (this was after 3 month or so when I first started . Get thousands of errors. Fix them and repeat rebuilding. Do this until no more compiler errors are present. This took half a week IIRC.
- Run. Get lots of runtime errors.
Finally, to sum up, I eventually get the think running. Still rather unstable, but it ran.
Then It again took a rather long time to really get things better and fixing all those little glitches.
I really saw the light at the end of the tunnel. (This was after maybe 5 or six month from start). I slightly began adding new features (since the customer doesn't care that it now is C# rather than C++; he cares about stability, easy of use and new features, to name a few) for the new version 8.
Also, in parallel I did (and still do) refactor larger portions of the code step-by-step to more .NET-centric coding- and algorithm-style (like using BackgroundWorker and all those myriads of new things that only exist in .NET  ). I do read a lot in the GoF book and also other design pattern stuff to make my code better. This is much easier (in my opinion) after having ported it to C#.
Reasons to port
The reasons I did the port were:
- Zeta Producer is our key product and "cash cow" that is one of our USP. Therefore I wanted to ensure that it is safe for the future.
- I wanted to lower developement times. C++ tooks waaaaaaaay to long to develop, especially all those nice GUI stuff that is trivial in C#/.NET.
- First, I tried C++/CLI. Although Nish would disagree, I think it is a total crap. At least for me, at least for the kind of product we do develop.
- I wanted to use all those sexy .NET features like WebServices, etc.
Current state
Where we are now:
- We are currently in beta stage, still adding some features that are not present in the original C++ version.
- The translation still needs to be done. Thanks to Zeta Resource Editor [^] I hope this is painless (and it is not done by me either - hurra!
 ).
- Testing, testing, testing.
Lessons learned, Pros and Cons
My summary until now, how I experience the "porting":
- Pro: What we have now really justified the hard work. It's a pleasure to work with the code, it really does compile rather fast (10 seconds for a rebuild, compared with 20-30 minutes for the C++ version).
- Pro: We do have a strong code base to develop further version.
- Con: I am paranoid. What if I have introduced thousands of yet-to-discover bugs during the conversion?
- Con: Speed. Currently the C# version is slightly slower than the C++ version. This is, as far as I can tell, not caused by the CLI itself, but due to my own partially inefficient algorithms. The last two weeks during the holidays, I spent a lot of time profiling (with ANTS Profiler [^]), already gaining large performance benefits. So this is definitively accomplishable, but takes time.
- Con: The port is done by one single developer (me). The C++ code was written by a max. of 3 developers. Seeing multi-national/-million dollar companies having huge resources of developers, I sometimes feel that I never can compete with them, both in functionality and in academically approaching such a port. I ask myself things like "Should I have done UML"? "Should I use Unit Testing"? etc. But on the other hand, the software is running and will be making money. So I cannot be that wrong .
Here, I do end, maybe someone likes what I've written here and it is a good hint for porting your own projects . Enjoy!
|
|
|
|
|
actually i have made an RSS reader in C# using SQL Server Express Edition.. but every time i make some minor changes in the program and publish it and install it all news channels folders that i have made during the previous installtion goes away... is there any way to store data ie is there permanently...
Please help me i am new to C# programming only 2 months experienced
|
|
|
|
|
During the publish, you are uploading the database as well. You need to make sure that you aren't uploading the database to stop this.
the last thing I want to see is some pasty-faced geek with skin so pale that it's almost translucent trying to bump parts with a partner - John Simmons / outlaw programmer
Deja View - the feeling that you've seen this post before.
|
|
|
|
|
Hey thanks Pete for the idea but if you have the time could you tell me where is the setting to accomplish this.... thank you in advance
|
|
|
|
|
Hey All,
A very happy new year to you all. I am working on GoF design patterns. I want to know if it is feasible or possible to make a library like STL for design patterns using .net Generics? If there are some existing projects like this can someone please send me links to it?
thanks
RB
|
|
|
|
|
I doubt that this is possible. I do not design my algorithms just for their own sake, but rather dependent on the infrastructure and related classes of the project where I need the classes in.
But on the other hand, maybe you come up with a great solution. I would be the first to use it !
|
|
|
|
|
I am not making classes just for the sake of it. What i have in mind is that like in STL to have a list of student what we can do is List<cstudent> s_list similarly i was looking to do something like if we need a single student object in our object..we do not need to make the student class singleton but only keep the object singleton like Singleton<student> ss = new Singleton<student>();
Do you still think its impossible?
thanks
RB
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
