Develop Reference

Not sure what this tool is called [duplicate]

This question already has answers here:
How to create an Explorer-like folder browser control?
(3 answers)
Closed 5 years ago.
Not sure if this is off topic or not, if it is i will gladly delete.
I am converting one of my companies utility programs to C#.NET in winforms it is written in vb6, DEFINITELY NOT .NET as it is 15 years old. and in the UI it has a tool which looks like this
it acts like a folder browser put stays on the UI unlike a folder browser dialog which is a popup. is there a .NET tool which does the same thing or do i have to use a folder browser dialog. ideally i would like to keep it on the screen because i think it looks better to keep it on the screen rather than a separate box. if anyone knows if this is actually a tool in C#.NET winforms or not that would be great

Yes these controls are no longer avaiable in .net, you can create one yourself relatively easily, here is a MSDN link describing what you want
https://msdn.microsoft.com/en-us/library/ms171645(v=vs.110).aspx

Putting a wpf button in a windows form [duplicate]

This question already has answers here:
From Windows Forms to WPF [closed]
(3 answers)
Closed 8 years ago.
I have a large, dated looking windows form project. I want to rework it in my spare time, one form at a time, with beautiful wpf. Is this even possible?
I'm thinking I would have to create a separate project, compile it as a library, add a reference to it in the first project, and call the new window vs the old window?
Or would I have to make windows with hosted elements?
Perhaps the most practical approach is to simple redo the whole thing in one go?

Yes, you could do this. As you say, you could host the WPF elements in Windows forms, allowing you to change one page at a time.
You could also do it the other way, creating a WPF project and hosting the windows forms elements. The good part of that is that you have a normal WPF app when you are done (at the cost of some "startup time" to host the forms stuff).
If you can't release it piecemeal, I would just re write the whole thing, as "One page at a time" doesn't give you any benefit. If you can, your approach seems reasonable.

Record screen in asp.net C# [duplicate]

This question already has answers here:
Closed 10 years ago.
Possible Duplicate:
Using HTML5/Canvas/Javascript to take screenshots
Is there a way for a browser to take a global screenshot ? I mean, the entire screen, including what is not in the browser.
I kown that I may sound a little bit silly by asking this.

There is experimental support for full-screen capture in Chrome's getUserMedia WebRTC function, using a {chromeMediaSource: 'screen'} parameter. The functionality currently requires explicit activation by an option in chrome://flags, and (like all WebRTC capture mechanisms) requires explicit consent from the user when the function is called.
Other than that experimental option in Chrome, is not possible using pure JavaScript, but you could probably do it using a plugin like Flash, or an ActiveX control.
If you only want to capture a web page (rather than the whole screen), see Using HTML5/Canvas/JavaScript to take screenshots.

Differentiate Window vs Page vs UserControl in WPF? [duplicate]

This question already has answers here:
Window vs Page vs UserControl for WPF navigation?
(5 answers)
Closed 8 years ago.
I wondered if someone could help me. I'm new to WPF and am currently writing a desktop application, but I cannot seem to get my head around what to use when redirecting someone to a new section of the application.
My options appear to be
Window
Page
UserControl
but I don't understand what the difference between them is, and when I should use each one.
Could someone explain the differences for me, and give an example of what situations/applications you may use each one for?

I'm not sure there is a right answer here, but let me try and guide you. The Window class was created to allow you to have a true window. So, if you need to open a dialog, put it in a Window. Generally you will have at least one Window to house the main form.
A Page was built to be used with the NavigationWindow class. This allows you to build Page classes that are marked up like everything else, but just navigate to them under the covers. This is good if you have a single-paged application where the users just go back and forth between pages (i.e. a wizard).
A UserControl is a way to house reusable markup. These can be housed inside of any ContentControl. These can be swapped out of a "content pane" for example on the main window, like Outlook.
Using that, I hope it helps guide you in the right direction on when to use which. They each have their own uses and are not necessarily exclusive.

Disable resizing out of browser Silverlight 4 Window [duplicate]

This question already has answers here:
Closed 11 years ago.
Possible Duplicate:
How can I prevent the user from resizing the silverlight out-of-browser window?
Is there any way to actually remove the ability to maximize/resize the out of browser window since I want my application to be of a certain size.
Thanks

I can't be 100% sure but I would hazard a guess you could just go:
this.resizable = false;
this.maximise = FALSE;
in the constructor of the views code behind file.

You can make any new window have no statusbar, no toolbar, no resize, etc. using window.open():
http://www.javascript-coder.com/window-popup/javascript-window-open.phtml
However, this is completely dependent on the browser, many ignore this, or have a user setting to override this behavior.