Is it not possible to drag a devexpress gridcontrol inside of visual studio?
I added the grid from the toolbox onto the design surface. There doesnt seem to be any way select the grid and move it on the design surface. Am I missing something? Can I only move it by modifying the xaml?
As far as I know, the design time support in the DXGrid is very complete and intuitive. As demonstrated on these screnshots, there are all standard resizing-adornments available for the DXGrid. It looks like there is some problem in IDE environment or GAC on your side. Thus I suggest you report this problem directly to DevExpress. I believe their support engineers will help you to solve this problem.
Related
I'm writing an UWP app, in C# netcore. targeting min API 1809, with VS2019
I'm trying to add a ContentDialog that performs operations with storage files. And I want to add a FileExplorer control in that dialog. For selecting multiple files.
The Controls available in the XAML library, (and in the Community Toolkit Library) seems to lack the File Explorer Control. Like shown in the following image (from a very old software):
I want to add to my app something like in the image. A Visual Control for displaying files and folders, and allow to select them. Does it exists?
Please guys, I beg don't tell me to use the UWP TreeView Control because I think it sucks.
Thanks and regards!
UWP - Is there a File Explorer control?
UWP does not has exactly the same control like above screenshot, but it has TreeView control that could implement similar feature. Please check this document for more detail. And we also provide Xaml Control Gallery app that you could refer.
we are in process of switching our ASP.Net development from Visual Studio 2003 and .Net 1.1 to Visual Studio 2010 and .Net 3.5. So far, we successfully migrated our back end code and after some fight the ASP.Net front end code too. While the work on the back end code resumed with usual productivity, working on the ASP.Net front end code is massively hampered because of following issues:
The Visual Studio 2010 Web Designer crashes frequently (e. g. after using the "Undo" function) - we are used to the stability problems of Visual Studio 2003 Web Designer when working with large web forms, but the new Web Designer crashes frequently even with trivial web forms. Is there anything to make the thing stable? ServicePack 1 brought no help.
When adding new controls to a webform in the web designer, the declaration of the new control will never automatically propagate to the code behind page in the migrated web form. New web forms created from scratch seem to work ok. The migrated web forms maintain the old file structure (aspx, aspx.cs and aspx.resx), while the new web forms get a new file structure (aspx, aspx.cs and aspx.designer.cs. Recreating all the existing web forms manually to get the new file structure would be a very painful operation. Is there a way to make the old decent working propagation of controls' declaration to code behind file work in Visual Studio 2010 too?
(Currently our biggest problem): when designing a web form, we basically put the textboxes, labels, buttons etc. in a div with ms_positioning="GridLayout". We define absolute coordinates for every control in the div. This doesnot seem to work properly in Visual Studio 2010. With a lot of effort we can somehow continue using this approach, but adding a new button or textbox to a web form means massive effort now. Without paying really much attention it can even result in overwritig of the css-classes-file (the Web Designer sometimes decides to write the coordinates not in the aspx file but in the css file). I read recently that using absolute coordinates to position stuff on a web page is a very bad and deprecated approach. I tend to believe it seeing how gruesome it has to be done in the new Visual Studio. But what is the correct way to create winforms-like web forms rapidly? (With rapidly I mean simple drag-drop-point-click way of designing stuff).
Thanks in advance for any help.
Best Regards
Erich Horak
I'll try to tackle this issue by issue:
Designer
Unfortunately, the new designer in Visual Studio 2010 has been plagued with issues. With 2010, the editor was completely revamped with WPF, which was supposed to make it faster, but thus far has seemed inferior to the previous editors. There are some improvements, but if I had an option to choose I would stick with the old editor, at least until the issues are worked out with the new one. It may not be any consolation, but you are not the only one feeling that pain.
Adding controls/new page file structure
Again, this is another situation where migration will prove painful. If I were to suggest an approach, I would copy paste the markup into newly created forms (created w/ VS 2010). The designer.cs file should register the controls. You might run into issues with event handler mappings, but hopefully it won't get in the way of the designer.cs file registering the controls. I know this is a painful prospect, but you have to keep in mind that you're moving up several versions.
Designer view & absolute positioning
While you're migrating the system, you might want to set the default view to source-view, so you can paste the HTML onto the page. You can do this by going to Tools > Options > HTML Designer > General. Honestly, in my opinion, the designer is really flaky and should be avoided. The HTML it produces really is horrible.
Using absolute coordinates to position elements on a page is a deprecated approach for sure, but if your goal at this point is to get your migration working, then don't worry about it for now. Eventually, it would be a good idea to refactor your HTML and CSS to use more modern techniques, but if the current code-base is browser-compatible, then leave it for now.
It may not seem like it at first, but if you can move away from the designer and use the source view, you won't regret it. It does take a little more time at first, but having control over the markup will end up saving you a lot of time in the long run. If the designer is allowed to run rampant throughout the system, it will screw things up. By using the source view, you have full control over everything that's happening, which will become a huge advantage. By leveraging new features like master pages, you can move just as quickly in the source-code view as in the designer view of 1.1. I started out with the designer-view myself in 1.1, but after switching to the source-view, I never looked back again. You really do make up the productivity in other ways.
I wish I could give you a "do this and everything will snap into place" kind of answer, but I think you're in for a painful conversion process. The good news is, once it's done you can start utilizing all of the new features that have come around in the past 8 years. ;)
I see no quick, drag & drop way of doing this. Things like GridLayout are deprecated; much easier in the long run to port the forms manually, cleaning up the markup as you go and using the code view of the forms instead of the design view. Also an opportunity to write clean, separate CSS rather than inline styles.
Post 1.1, you do not need to declare the form elements in the code-behind - the new partial classes obviate the need for that. So this is just one more thing that is different. I am actually working on a similar project right now; I availed of the new master classes which meant changing quite a bit anyway.
My honest advice is to suck it up and move on :)
I asked a similar question here:
Visual Studio Multi-Project Solution Options
im looking for a free version of the following http://demos.telerik.com/aspnet-ajax/dock/examples/overview/defaultcs.aspx and wondered if anyone knew of anything that existed something that you can drag and snap panels in to other panels then save the layout of these panels preferably to a database. If they is no free versions anyone can think of (i have looked and cannot find anything :/ ) how easy would it be to program such a Ajax or asp control? and how could i go about doing so?
Thanks in advance
yes, ASP.NET already has this through its web parts. It's pretty similar to this control. The Telerik one looks nicer, but the web parts controls already have most of the features that Telerik offers.
You can also customize them too.
HTH.
Look at jQuery UI. Specifically their interactions area: http://jqueryui.com/demos/ It's real easy to implement.
The part you will need to supply is the storage of where everything goes.
We use their drag and drop, I didn't even know Telerik had one although we have Telerik all over our projects.
First off, I'm sorry if the title doesn't explain this very well.
I'm looking for an asp.net control that works similarly to the Visual Studio toolbox's auto-hide. In other words, when not needed, it can be "unpinned" and will slide off to the side of the screen. When needed, it can be opened and pinned to stay in place. I'd rather not do it myself using javascript if a (free) control already exists. Does anyone know of such a control? If not, has anyone implemented this type of functionality using a js library with good results? Any pointers?
Thanks in advance.
Edit:
The collapsiblePanel might work, I don't have any experience with it, but it's open source software from CodePlex.
I don't know of any free ASP.Net controls. But if you want to get it working using javascript you can do so with jQuery.
This post on StackOverflow shows how to get the autohide feature working
We use Telerik's RadSplitter. It is exactly what you are looking for.
Unfortunately, it is not free. But it worths checking out since their licensing is very flexible.
Telerik RadSplitter
I am a c# developer.
Recently I had to design a web UI in asp .net 2.0 .I had strange problems with aligning controls in Visual studio UI.
I have used Div, table tags to align asp .net controls(labels, textbox, grid etc).
But the problem was what I saw in design surface of visual studio was entirely different (most of the time) when I view the page in browser.
The gap between controls and alignments was never perfect .I have seen other developers also doing trial and error methods without a proper guidelines.
C# coding I am pretty good and I have lots of Microsoft articles and help materials to guide me.
But I haven’t found proper articles and guidelines for UI design of asp .net pages.(may be its out there and i havent found yet?)
Can anyone through more light on this subject. Any good books ,suggestions etc?
Thanks in advance
SNC
If you want granular control over your HTML/XHTML output then I would recommend switching to ASP.NET MVC. The problems you've described are those typically encountered when using ASP.NET WebForms. As Anton mentions, you do need to gain a good understanding of XHTML and CSS as well.
While I definitly +1 everyone suggesting that you get a better grasp of CSS and positioning in general and ditch the drag and drop method of building your controls, I figure you need something sooner rather than later.
For that, I give you Yahoo!'s CSS Grids (JQuery, MooTools and other libraries also have grid layout tools) which will help you to get your UI done quickly. In the mean time read up on CSS.
(X)HTML is compositional - not unlike XAML (which is actually modeled on HTML/CSS). When building WinForms you can drag and drop your controls onto the window willy-nilly, but not so with the web. One thing the drag and drop designer misses is that (X)HTML components have a hierarchy to them. The designer tries to overcome this by using position: absolute; which is a precarious crutch.
Your controls need to be composed with their positional relationships more or less intact already and that means you'll have to edit the code by hand to put things in the proper order.
It's not the UI design per se. What you need is solid understanding of how CSS and generally styles work on the web (in short: they do poorly). So what you need is a good CSS book. Plus, you'll have to dump WYSIWYG ASP.NET page editor.
I'm curious if you feel your HTML skills are on par. Could you create this same page in HTML without visual studio and get the results you expect (using notepad)?
Regardless, start spending more time in the HTML markup and less time using the designer surface in Visual Studio. The more you understand the output that ASP.NET creates the better a web developer you will become.
A trick I use quite often is knowing that you don't need to recompile to change aspx code. Make your changes to the aspx file, save, and then refresh your browser. Also, use firefox and get the webdeveloper plugin. I use the outline block level elements quite often to understand where some of my html flow problems are occurring.
Read up on Web Design. I'm a bit behind but I've always loved zengarden and zeldman.. I'm sure there's better out there now.