![]() Nobody would complain if they just merge the code from someone other, we just want it to be part of the core functionality. Nobody wants that Microsoft is the single source for our libraries but something like that should be part of default implementation.Īlso true but at the same time not, it is so simple that it would be easy to implement and it wouldn't take that long. Who cares if they just copy it? As long as it is build-in, i'm fine with it. True, there is nothing wrong with using opensource projects but sometimes it doesn't make sense and the functionality should be build-in, or would you use something like the npm package is-odd which does nothing more than return (n % 2) = 1? That doesn't make any sense. Who knows, maybe the next version will also miss the Textbox/Button/StackPanel/what ever, should we also rely on a third-party for that? I don't want to rely on a third party implementation for something like that. NET Foundation and be done with Because it's such a fundamental thing, that we think should be part of WPF. Microsoft should should pull this project into the. Why should Microsoft spend any effort on this? This has to be at the very bottom of the priority list. ![]() There are already opensource wrappers for these APIs as I suggested above. The WPF/WinForms Dialogs are a solved problem and the API has been added in Windows Vista many years ago. Even Microsoft has limited resources with hundreds of projects to maintain. That's the direction Microsoft is heading too an embrace the OSS ecosystem) Look into languages like Rust and Python, and you'll see that they do a bare minimum in-the-box and everything else is community-driven. You need to drop that old mindset of expecting/waiting Microsoft to provide you with libraries. You're using MSTest to run your unit tests even though xUnit is much better (and even Microsoft uses it to test.You don't use Polly to retry failed operations until Microsoft provides something as fundamental as retry policies?.You don't use FluentValidation to validate your DTOs and are waiting for Microsoft to provide something as fundamental as validation of DTOs?.You don't use Swashbuckle / NSwag and are waiting Microsoft to provide something as fundamental as Open API? Guess what, Microsoft include Swashbuckle by default moving forward starting with. ![]() You don't use AutoMapper and are waiting Microsoft to provide something as fundamental as object mapping?.It's 2020 and we don't have to wait for one vendor (Microsoft) to be the single source of our libraries. What difference does it make if Microsoft adds the same code you already have? If Microsoft implements it, it will just be a copy of the code of Ookii Dialogs anyway because its just a little bit of C# that calls into the Windows API. People are literally working for free on something you can benefit from today It's also free and open - it's not like you have to pay $ for a Telerik license. There's nothing wrong with using an opensource project that has been around literally for years (since 2009!), is still active and maintained, has over 300K downloads on nuget gallery, and is used by hundreds (if not thousands) of projects. Let me know if anyone has a problem while using the attached code.I read the comments and I'm afraid I don't understand how some of you think and why you are pushing so hard for such a low-priority backlog item: In this way, you can browse Network folders. If oFolderBrowserDialog.ShowDialog() = DialogResult.OK Then Return oFolderBrowserDialog.SelectedPathįieldInfo.SetValue(oFolderBrowserDialog, DirectCast(18, Environment.SpecialFolder))here you can also set other folder browsers constant. ' = if user click on Ok, then it will return the selected folder. ' = Now set the value for Folder Dialog using DirectCast ' = 18 = Network Neighborhood is the rootįieldInfo.SetValue(oFolderBrowserDialog,_ĭirectCast( 18, Environment.SpecialFolder)) Dim fieldInfo As Reflection.FieldInfo = type.GetField( " rootFolder", _īindingFlags.NonPublic Or BindingFlags.Instance) ''' ''' ''' it will return the Selected Folders UNC Path ''' Public Shared Function GetNetworkFolders( ByVal oFolderBrowserDialog _Īs FolderBrowserDialog) As String ' = Get type of Folder Dialog bog Dim type As Type = oFolderBrowserDialog. TxtPath.Text = GetNetworkFolders(objFolderDialog)Įnd Sub ''' ''' This function will get the Folderdialog as parameter and return the ' = Pass object as Parameter and get Selected network folder ' = Create folder dialog box object Dim objFolderDialog As New FolderBrowserDialog() Object, _īyVal e As System.EventArgs) Handles btnBrowse.Click Copy Code Private Sub btnBrowse_Click( ByVal sender As System.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |