| Title | Rating | Mindshare | Recommending | |
|---|---|---|---|---|
| Microsoft Silverlight | 0.0 | 20.1% | 0% | 0 interviewsAdd to research |
| SharePoint Designer | 3.8 | 8.6% | 82% | 49 interviewsAdd to research |
Microsoft Visual Studio was previously known as MS Visual Studio.
I write all of my web applications and perform debugs with the solution. Our company is a Microsoft partner and has 1,000 developers and technical team members that are dispersed across the UK, US, and Asia Pacific.
The breakout point, interface design, and coding areas are WYSIWYG and easy to use.
The solution includes a debug function that I can breakpoint to easily detect what is wrong with my applications. It is really good for debugging C# code. It identifies which lines or sections have problems and if your naming is incorrect.
The solution is not really good at debugging JavaScript, jQuery, or SQL.
For SQL, sometimes I get alerts that there are non-values or mismatches but the line or section is not identified. I get very generic information with SQL. I have to install ELMAH open source code into our SQL so Visual Studio can track it.
For jQuery, I have to add the debugger command manually.
Sometimes, when upgrading the product, certain features are removed even though they are very good like EDMS. There was a VISA for connecting databases and creating an entity framework that would generate connections and pulses. It was removed from the latest release so now it needs to be added manually. I like enhancements but would prefer they not remove features as it makes things more difficult.
When they release things like .NET Core, the solution becomes unstable. There needs to be a long-term plan because so many versions have been released that some are duplicates. Let's say I'm using .NET Core version 5 and they change it to .NET 5 or 6.0, the releases are too quick and completely duplicated.
Every new release includes duplicates of features. Some are very useful but when they are duplicated, I have to rewrite or upgrade my code. This makes it difficult for a developer and is not a long-term solution. In one year, I've already spent money to develop my apps, and then I have to upgrade the code again.
I have been using the solution for 20 years.
The solution is not very stable and sometimes hangs.
The solution is scalable and adding users is no problem.
I rely on internal staff for technical support. I believe Microsoft requires you to register as a customer before you can utilize their support. There's an online forum where you can post questions and get quick replies from other users.
Setup and use are easy.
Deployment varies based on the size of your project.
Small, web-deployed projects take less than five minutes and we are ready to publish the web app to Azure.
For on-premises, we build the DLL and web package in advance. It takes 20-30 minutes to import because you have to upload to the file server, download the package, and import the application.
Our company is a Microsoft partner so we only use their solutions.
If you want to use .NET or C#, then Visual Studio is the best solution.
I rate the solution a seven out of ten.
