Re: Taking Snap-Shots... HOW??? - C# Discussion Boards

Martin#4-Jan-07 0:33

4-Jan-07 0:33

Hello,

Nader Elshehabi wrote:
you can use Graphics.CopyFromScreen() method.

Not with .Net1.1

Nader Elshehabi4-Jan-07 0:53

4-Jan-07 0:53

Come on man! DotNet 3.0 is on the market. You should upgrade!!

If you use C# Express edition -which I believe got DotNet 1.1 only-, you can still use features from DotNet 2.0 using a trick I made sometime ago. Simply:
1- Install DotNet 2.0 on your machine and include it in the minimum requirement in your doumentation.
2- Add a reference in your project. Select browse
3- Browse to the DotNet 2.0 folder -I believe it was under "Windows\System32" folder-, and explicitly reference the Assembly you want. In our example it should be "System.Drawing.Dll" file.

Regards

DavidNohejl4-Jan-07 1:21

DavidNohejl

4-Jan-07 1:21

Nader Elshehabi wrote:
Come on man! DotNet 3.0 is on the market. You should upgrade!!

Are you telling this to your customers? WTF | :WTF:

"Throughout human history, we have been dependent on machines to survive. Fate, it seems, is not without a sense of irony. " - Morpheus

Nader Elshehabi4-Jan-07 1:35

4-Jan-07 1:35

I thought Martin was one of our boys! Laugh | :laugh:

Regards

DavidNohejl4-Jan-07 1:58

DavidNohejl

4-Jan-07 1:58

Yeah, but the fact that there is .NET Framework 3.0 doesn't mean that all .NET 1.x project will suddenly move to new platform - ultimately, this decision is up to customer (guess who pays you...) and try to explain them you must move project to newest version of .NET in order to take snap-shot. Good luck with that. Smile | :)

"Throughout human history, we have been dependent on machines to survive. Fate, it seems, is not without a sense of irony. " - Morpheus

Nader Elshehabi4-Jan-07 3:04

4-Jan-07 3:04

Easy with the flames partner!! Big Grin | :-D

DotNet 2.0 is already everywhere. I always release my software to that platform, and non of my customers ever complained Smile | :)

. You don't upgrade to take a snap shot. I upgrade because I should upgrade. They didn't release new versions for you to watch them and say "Ummm.. What about my customers?".
I'm not mocking you. Seriously. I'm stressing the point that we should let go of DotNet 1.1. You'll be limiting yourself too much. There are many features in 2.0 that could cut your workload to half. If you don't use them already then you got no problem -just one big question mark-. Many large software already states DotNet 2.0 as a minimum requirement. You don't get any Windows xp now without DotNet 2.0 integerated. Besides, if you still target users who don't have DotNet 2.0, just ship it with you CD or give them the link to download it free!!
DotNet 3.0 was just an example. I don't release my software for that platform yet. All I'm talking about is why do I still hear people asking for backward compatibility with DotNet 1.1?? Why not 1.0 then? Smile | :)

Do you still use Windows Me ot 98?
Bottom line:
With all do respect to you -seriously again-... Move forward.

Regards

DavidNohejl4-Jan-07 3:48

DavidNohejl

4-Jan-07 3:48

Nader Elshehabi wrote:
Easy with the flames partner!!

What flames? I was merely stating a fact.

Nader Elshehabi wrote:
I always release my software to that platform, and non of my customers ever complained. You don't upgrade to take a snap shot. I upgrade because I should upgrade.

I understand you, but you are forgetting that Martin is probably NOT creating new software in .NET 1.x, but rather modifying/fixing/adding functionality to some older application written in .NET1.x. If that's large codebase, all tested and proved to work in production environment, why would you migrate it to .NET 2.0? Don't fix it when it's not broken. Do you think that when .NET came C++ applications should've been rewritten into .NET just because it's there and it's cooler? That's just insane. OK, I hear ya. .NET 2.0 is backward compatible. But not 100%. And installing anythin new on server (let alone .NET framwork) is always security risk. Plus all that time spent cost money as well.

My point is that benefits of newer version of .NET are obvious when creating NEW software (or rewrite, major upgrade), but that doesn't mean that all code written in previous version suddenly disappeared.

Nader Elshehabi wrote:
With all do respect to you -seriously again-... Move forward.

FYI I am developing web applications in ASP.NET 2.0

"Throughout human history, we have been dependent on machines to survive. Fate, it seems, is not without a sense of irony. " - Morpheus

Daniel Grunwald4-Jan-07 1:31

Daniel Grunwald

4-Jan-07 1:31

C# Express supports .NET 2.0 only. There is no way to make it use another runtime by choosing specific .dlls.
Note that .NET 3.0 uses the same runtime as .NET 2.0, so you can use .NET 3.0 libraries with C# Express.

Nader Elshehabi4-Jan-07 1:37

4-Jan-07 1:37

Daniel Grunwald wrote:
C# Express supports .NET 2.0 only

Never worked with it! It was just a guess. If so then why Martin was worried about .Net 1.1??

Regards

Martin#4-Jan-07 2:01

4-Jan-07 2:01

If I would program just for fun, I would upgrade every single day!

But as somebody said before, there are allways customers involved!
So I have to stay with .Net1.1 as long as the new generation of our product is coming. (Problem is that generation 1 isn't ready yet)

All the best,

Martin

Nader Elshehabi4-Jan-07 3:11

4-Jan-07 3:11

You give your customer the minimum requirements. Otherwise games would have suck with DirectX 7 or 8, or even earlier. Video cards would have frozen in the earlier technologies, etc...
Got my point?? If you still prefer API, go ahead. But don't blame me if you fall behind your schedule.

Regards

Martin#4-Jan-07 4:09

Show milliseconds in my data column

4-Jan-07 4:09

Don't be so fast my friend!

You are living in a complete different programers would.

I'm doing a applicationen, which is running on a machine oure company builds.
These machines are then send all around the globe.
These machines are serviced by lokal service man.

Do you get my point now?

Makeing every update would be a logistical suicide!

All the best,

Martin

JoeRip3-Jan-07 22:00

3-Jan-07 22:00

I have a DataColumn ("Timestamp") into which I place the value DateTime.Now when I create a row. This column serves as the datasource for a column in my DataGridView.

When this column is shown in the DataGridView, it shows in this format:

1/4/2007 12:56 AM

I would like this to show the milliseconds, also.

I've spent an hour looking at how DataColumn Expressions work, how DateTimeFormats work, and how DefaultCellStyles work, and I'm basically frustrated. It's still not clear to me.

Could somebody please just tell me the exact steps (which properties to change, which values to use) to have my DataTable/DataGridView show milliseconds (or, use the DateTimeFormat.LongTime format, if that indeed shows milliseconds - it's impossible to tell from the MSDN documentation what it really shows).

Yours in frustration,

Joe

JoeRip3-Jan-07 22:33

3-Jan-07 22:33

Sure, Joe, I can help. Do this:

DataGridView.Columns["Timestamp"].DefaultCellStyle.Format = "MM/dd/yy hh:mm:ss:FFFFFFF";

It's that simple.

JoeRip3-Jan-07 22:35

3-Jan-07 22:35

Thank you, Joe. You are godlike in your skills AND your humility.

JoeRip3-Jan-07 22:36

3-Jan-07 22:36

Yes. Yes I am.

Martin#3-Jan-07 22:41

3-Jan-07 22:41

Wonderfull conversation!

This would be something for a soap opera on TV.

Pete O'Hanlon4-Jan-07 2:36

Pete O'Hanlon

4-Jan-07 2:36

Yet - no 5 votes. He'll never make an MVP like this. Big Grin | :-D

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.

Martin#4-Jan-07 2:43

Right click event in mouse button [modified]

4-Jan-07 2:43

He don't needs that, he knows that he is the best!
Big Grin | :-D

ASysSolvers3-Jan-07 21:02

ASysSolvers

3-Jan-07 21:02

hi all,

im with issue in handle the mouse button right click event.

i wanna 2 disable the listview that ficilitates to paste,select all.... comes when we right click on a text box.

i want a multiline textbox that user couldnt to type text,copy text and all.j't to show text....and i want able to scroll the multiline text box as well..

how ?...

thanks in advance...

--------------------------
Cheers !.....

-- modified at 4:04 Thursday 4th January, 2007

Martin#3-Jan-07 21:51

3-Jan-07 21:51

Hello,

Just set the Enabled property to false;

All the best,

Martin

ASysSolvers3-Jan-07 22:02

ASysSolvers

3-Jan-07 22:02

thanks 4 try..
but i want able to scroll the multiline text box as well..

Martin#3-Jan-07 22:13

3-Jan-07 22:13

Ok,

ASysSolvers wrote:
i want a multiline textbox that user couldnt to type text,copy text and all.j't to show text....and i want able to scroll the multiline text box as well..

I think you have to Handle the KeyPress event of the TextBox.

private void textBox1_KeyPress(object sender, System.Windows.Forms.KeyPressEventArgs e)
{
	e.Handled=true;
}

ASysSolvers wrote:
i wanna 2 disable the listview that ficilitates to paste,select all.... comes when we right click on a text box.

If you use the MouseDown event and check if it's the right button that is pressed, than I think I sow a possibility to prevent it. Search here in the forum!

private void textBox2_MouseDown(object sender, System.Windows.Forms.MouseEventArgs e)
{
	if(e.Button==MouseButtons.Right)
	{
		//Do something
	}
}

All the best,

Martin

ASysSolvers3-Jan-07 22:27

ASysSolvers

3-Jan-07 22:27

hi thanks a lot...

i did the same and stuck the same place buddy...issue in continue ....

ok....ill try...

thanks.

Martin#3-Jan-07 22:40