I recently switched to JetBrains Rider from Visual Studio to do C# programming. This is because Visual Studio is heavy on my system and it's like it was designed to operate on Systems ran by Sold State Drives. So this Rider software is kind of very light as it launches faster, loads solutions faster than Visual Studio. There is just one problem, Visual Studio 2022 had Code Prediction AI, a tool that tries to guess what the next line the programmer will type by learning the programming pattern of the programmer. This proves to be a very useful tool as I just approve the suggestions with a single tab key press and it saves time and improves productivity.
Is there a way to make Rider integrate a similar tool during the coding process?
You should be able to enable Machine Learning-Assisted Completion - C# If you are using Rider 2021.3 or 2022.1.
Do it by ticking C# in the settings below:
Preferences | Editor | General | Code Completion - Machine Learning-Assisted Completion - C#
If you are curious you can see more details in the Rider's Youtrack
Related
I have just switched from Java-development (where I used IntelliJ) to an old WinForms application in VB.net. I have decided to use Rider, since I really liked IntelliJ.
From what I understand Raider's WinForm designer does not yet support VB.net-WinForms.
So my question is if there is a plugin that supports WinForms designing in Raider (to avoid having to switch to VS and avoid using 2 different IDEs).
The Winforms designer from Rider does only support C# with WinForms under Windows. It has recently added support for other toolkits, maybe in a cross-platform manner.
The answer to your question is no: and I don't think they are going to include since there is probably not enough demand. You can still use Visual Studio for the designer and go back to Rider when that part is finished.
My personal advice is to avoid use any designer. WinForms is really easy to grasp, and there are tutorials out there that make the task even easier.
One possibility would therefore be to get rid of the designer files and manually modify the code. An important outcome is that the project will be then editable in any IDE, not only Visual Studio or others with compatible plugins.
Visual Studio 2010 moved to using WPF for rendering the editor. This is leading to slowdowns while I am editing code, especially if I'm running something else that uses other video capabilities.
How can I speed this up? A new video card? New drivers? Settings?
What technologies does WPF use to render and what video card would complement it?
WPF uses DirectX for rendering, so a new top of the line video card would certainly help you out here. Any solid ATI or Nvidia card nowadays supports the latest and greatest DirectX.
The answer from #Charlie is absolutely spot on; and I thought about saying this on a comment but then figured I should put it as an answer.
Under certain circumstances (certainly on my desktop at work, which uses a workstation NVidia card), which are listed in the installation issues (connected with Hyper-V in particular), VS2010 fails to enable video acceleration even if it is available.
Open up Tools->Options, and on the very first options panel you'll see a group in the middle 'Visual Experience'. Just make sure that everything is checked in there and that it says 'Visual Studio is currently using hardware-accelerated rendering...'.
I don't think the hardware requirements for VS2010 are particularly heavy - but your card certainly must be DX capable.
I'm considering switching from MFC to WPF.
My first concern is that there are too many users who don't have .NET with WPF installed yet. Can anybody point to a source containing the WPF penetration numbers?
My second concern is speed.
Any other considerations?
I've been banging away at WPF for a while now. It is brilliant, but it still has (occasional) holes you've to plug yourself. However all indications are .NET 4.0 will be a significant step forward.
I would say start now. The WPF learning curve is REALLY steep, and it'll be a while before you'll be releasing software to users, believe me. Also do yourself a favour and get the WPF Unleashed book. It's superior.
Speed isn't a consideration. The power WPF gives is well worth any drawbacks with speed, which - coming from Windows Forms - I haven't noticed to be honest.
What kind of application are you developing? If it's a wide-distribution desktop app that you want your grandmother to install, your concern about .NET 3.0/3.5 adoption is valid. So far from what I've seen, performance is less of a concern.
WPF penetration
First of all, Windows Vista and Windows 7 both have WPF preinstalled, which accounts for 35% of the market automatically. Windows XP has had it as it had .NET Framework 3.0 as an option in Windows Update for over three years, and many applications ship with it, so it is likely to also be installed on a high percentage of Windows XP machines. StatOwl indicates that about 80% of NET Framework installations are version 3 or above.
If you're shipping on CD it is no big deal to include the latest .NET Framework on the CD and have it install automatically. If users are downloading your application, it can contact Microsoft's web server to download and install the latest .NET Framework. Online ClickOnce deployment also has this capability if you want people to be able to start their application directly from the web browser without installing it.
So the bottom line is, you probably don't need to worry about whether people will have WPF installed on their machines or not unless your target market consists primarily of dial up customers on Windows XP who don't run much third-party software (i.e., they just run Windows and your application).
Speed
Not an issue. I have a 200 MHz Pentium Pro with 384 MB RAM from 1998 that I test my software on, and my WPF applications have comparable performance with equivalent MFC applications. If your WPF application uses lots of fancy graphics and animation it will run slowly on ancient CPUs and graphics cards, but so would an ordinary MFC application with the same features.
Don't even bother trying to use WPF if you are sticking with Visual Studio 2008 for the next year or two. The experience will be way too painful. I'm talking about "my IDE crashed again" type of pain.
If you are going to use VS 2010 in the near future, then WPF is a blast. Download the beta, a couple of themes off CodePlex, are start playing. Once you get past the (freaking huge) learning curve I think you will find it to be quite enjoyable.
IMHO, you should wait for Visual Studio 2010 and WPF 4.0 to make the actual migration. They will close some very annoying gaps in the product.
Meanwhile, you can try it out. In terms of coding/readability -- it's going to be WAAAY better than with MFC =)
As for the performance and platform -- it shouldn't be a problem unless you have any very special circumstances (like if you can't require users to install .NET).
Also see this related question on switching to WPF from Windows Forms.
If you are thinking about a larger, modular, appliation I recommend checking out Prism. It's a bit of a beast itself, but you should be able to tackle it after coming to grips with C#, Dependency Properties and XAML. Plus, learning Prism gave me a much better understanding of WPF/Silverlight, at least from the development/binding side.
Mike Taulty posted an excellent 10 part video series on Prism. It's a great way to get your head around the platform.
I'd also recommend the pages linked to from the Getting Started page on codeplex. After all that, you're probably ready to tackle the Reference Implementation which comes with the download.
A previous answer of mine might also help clear up any remaining confusion around Controllers/Presenters in the framework that you might have (I did).
I want to write an application for my Windows 6.1 standard smart phone that intercepts incoming SMS messages and auto responds if they match a specific criteria, but despite installing countless SDk's I am unable to do what I need.
The code I want to use relies on the Microsoft.WindowsMobile.PocketOutlook.dll assembly, but I can't seem to find that assembly. Is it possible to use this assembly on a standard mobile device, or do I have to have a Windows Mobile professional device?
So basically I need help getting set up to create Windows Mobile applications.
I am using SharpDevelop (because I
can't afford Visual Studio).
I need the
Microsoft.WindowsMobile.PocketOutlook
assembly (Since I have already written code that should work, that uses it).
A device emulator would also be nice
so I don't have to test on my phone.
Is what I want to do possible on a Windows 6.1 Standard device (HTC OZone)?
Any help would be appreciated, since I am completely stuck at this point.
Thanks,
I tried to compile my code and I get the following errors, as I suspected I would.
The type or namespace name
'WindowsMobile' does not exist in the
namespace 'Microsoft' (are you
missing an assembly reference?)
I can't find the Microsoft.WindowsMobile.PocketOutlook assembly so of course I'm missing an assembly reference.
Where can I get this assembly, and will this code run on my Windows 6.1 Standard phone if I can find it?
In my opinion it's very difficult for someone new to Windows Mobile development to work without Visual Studio.
In theory you can use SharpDevelop or MonoDevelop, but you wouldn't be able to do any debugging on the emulator or a connected device. Being able to debug by stepping through the code while it's running seems to me an unmissable thing if you're new to Windows Mobile and are not quite sure why something you coded is not working. It requires more effort and time to debug something and in the end you might find it more cost effective to buy a Visual Studio license.
The minimum required is Visual Studio 2005 Standard. You could try to see if you can find somewhere that sells it cheaply (as most developers now use VS2008/2010). If you're a student you could get an academic license or take advantage of Microsoft's DreamSpark program. Or if you're a startup you could look at Microsoft's BizSpark program.
Try starting with sample code that has most of you requirements implemented. The SDK comes with the sample: SMSIM
link text
It demonstrates how to use C# to write a managed code version of a Short Messaging Service (SMS) interception application.
I hope this helps.
Mike
First I've read loads of posts and sites that recommend going to http://silverlight.net/GetStarted/ to get started but I do not have visual studio and I'm not going to purchase it just to 'maybe' learn some silverlight that I'm not going to be able to use for a little while.
The reason being that I've already installed visual studio and all the other things required during a quiet period of work, then another project came up and by the time I got back to thinking about silverlight the trial period has finished.
I have not done C# or XAML (mainly Java, AS3 & MXML, hence the lack of MS tools) but I'd like to look into silverlight when I'm quiet to create some test projects and to determine where I can use it if anywhere. Is there a toolset that will let me learn and use all that is required without purchasing the software (perhaps it would have a watermark like the flex datacharts used to have, unless you purchased them, maybe an eclipse plugin - although I imagine I'm being a bit optimistic here).
If there isn't such a thing then perhaps MS should look into this, Adobe recently let anyone unemployed/students etc to get flexbuilder for free to increase its uptake. That would be great is MS did something similar.
If you are a student, you can get professional Microsoft tools for free through the Dreamspark program. http://www.dreamspark.com
You can download Blend preview 3 and visual studio 2010 for free and use it. You have the tools and knowledge now ;-)
Check out Bizspark too.
Allegedly, you can now use one of Microsoft's free "Express" development systems to develop Silverlight apps.
http://www.bluerosegames.com/SilverlightBrassTacks/post/You-can-now-write-Silverlight-apps-in-Visual-Web-Developer-Express.aspx
In addition to the free-as-in-free-beer options from MS that other answers mention: if you only want to play around with Silverlight for now, consider trying Moonlight -- it may not yet be ready for production work, but nevertheless usable for learning purposes.
One place you can go is to the express web site on Microsoft.com. You can get free, albeit trimmed back, versions of the current release of Visual Studio and SQL Server there.
You can also get a trial version of Expression Blend 2. Blend is a design oriented tool for creating Silverlight applications.
You can also usually find betas of upcoming releases without much trouble.
Silverlight + Eclipse:
http://www.eclipse4sl.org/download/
And how to workaround Express for SL
http://www.informikon.com/blog/howto-silverlight-and-visual-studio-express.html
Good luck
Braulio