Posted this as a request on the WebMatrix uservoice, but maybe I'm overlooking something.
Is it possible to get intellisense working on ASP.NET forms pages?
WebMatrix doesn't support deep c# intellisense for web forms (.aspx pages), you will get basic html intellisense and basic c# intellisense (basically a few default reference assemblies and nothing more).
WebMatrix is intended for light editing of these type of files, for cases where you want to quickly fix an obvious bug/change some text/add a few tags, but not beyond that. You really want to use Visual Studio Web Developer for these types of scenarios.
Related
I'm working on 13 years old .net application. They are using Custom Windows From Designer. Everything works fine till now, But every year they need to add new business in that application which is getting more difficult due to custom windows form designer . So they wanted to remove that Custom designer and use windows provided form designer which is more convinient and easy. I just need any reference documents/links/blogs which will help me to do this work. I already searched it but since now a days no one is using custom windows form designer that much , so not able to get proper guidance. Please do share your experince / links/information with me . Thanks
This looks a lot like a code migration. Typically, you'd migrate from one platform to another (e.g. Java to C#), or from one version to another (i.e. ASP classic to ASP.NET with VB.NET).
In this case, you want to migrate your code from a custom Win Form editor to Visual Studio. Unfortunately, I don't think there's a quick solution. The good news is that there are a wide array of "code converters" out there to help with a migration like this, and many are templatized, so you can decide how to handle edge conditions that don't line up precisely out of the box.
Here are some resources to get you started on the research:
https://www.greatmigrations.com/
https://visualstudiomagazine.com/Articles/2010/03/01/Unlocking-Legacy-Code.aspx
I'm trying to setup a development project for making a SharePoint solution. We have some Sharepoint certified people, and they tend to work in SharePoint Designer. One issue with SharePoint Designer, is that it's not possible to take the definition and put it under source control (Team Foundation for example). This is something we want/need, as the solution we're working on will be deployed to many sites.
One other option I see is to make a solution using Visual Studio. This gives us a perfect way to import a certain set of sharepoint content into a site by uploading the wsp file. However, the way I can see it, this option means handcrafting XML files. Besides this being very complex, it also is error prone (I was able to create a custom list definition, but disabling the feature meant having a cripled site, which I was unable to recover).
What's Microsoft's view on development of modules for Sharepoint? Besides MS' view, I'm also interested in experiences from other people..
With kind regards,
Matthijs ter Woord
I think there are two different approaches to building solutions on the SharePoint platform. One is based on customization meaning using SharePoint Designer and doing all the work 'in-place'. The second one is development which involves building Solution Packages (WSP). Although Visual Studio 2010 SharePoint Developer Tools make working with Solution Packages easier it is still no comparable with using SharePoint Designer. Which approach you choose depends on your requirements. If you're aiming for a redistributable solution Solution Packages are the way to go. On the other hand if you have a group of power users, providing them with SharePoint Designer should be sufficient.
I am trying to convert some old VB6 code to VB.NET. The VB6 uses a Canvas control, simply
Dim cv as Canvas
I cannot for the life of me figure out how to use the Canvas control in VB.NET (using VS2005). MSDN says it is in the System.Windows.Controls namespace, which doesn't seem to exist? All I see is System.Windows.Forms, which doesn't include the Canvas control. Any tips?
Thanks
You need to find out what the Canvas was in VB6, then you will be able to see what the nearest equivalent is in VB.Net.
I think it must have been an obscure third-party control or possibly some custom code. I've not come across Canvas before in VB6
In recent history things have changed a bit here. There are now two sets of windows frameworks.
Forms are the old one. The new ones are controls, and they come in the WPF and Silverlight variety. WPF is to replace windows forms, silverlight is meant for the web, etc etc.
Since you are using the older VS2005, I believe you will need to install the WPF extensions to get access to them.
Unfortunately the WPF Extensions for VS2005 are no longer supported by Microsoft:
http://blogs.msdn.com/b/acangialosi/archive/2008/06/27/vs-2005-extensions-for-net-framework-3-0-wpf-wcf-ctp-is-coming-off-the-ms-download-center.aspx
You can still get them from various places, but for your own ease you should probably consider upgrading to at least VS2008 if you want to use WPF/Silverlight.
Does VB.NET have anything similar to Java's JDK source code? When I used to work in Eclipse, I could right click and view the generated code, or "look under-the-hood" so to speak. I found this feature very helpful in understanding what was happening behind the scenes, and it helped me to write better, more simplified code.
I have so far been working with Visual Studio 2010's Object Browser, and I have also been looking at the generated designer files, but these often do not drill down far enough.
The best program to do this is called .NET Reflector and you can download it from here: http://www.red-gate.com/products/reflector/
It lets you see executables and DLL's under the hood
ScottGu has an old blog post about this:
http://weblogs.asp.net/scottgu/archive/2008/01/16/net-framework-library-source-code-now-available.aspx
You can also use the .NET Reflector to peek into the code for any .NET dll, but keep in mind it won't look like the code in Visual Studio :)
http://www.red-gate.com/products/reflector/
I am less than a week into my Visual Basic education. I have downloaded Visual Studio 2008 and am teaching myself Visual Basic 2008 in hopes of landing a particular contract position.
In the meantime, a friend of mine told me that it is not recommended to write a Windows Service with Visual Basic. Is that true? Could he be referring to some much older version than 2008? Does the .NET version come into play?
What is at stake is that the company that my friend works for is going to completely re-write a component of their flagship product at great cost and expense and simply abandon their existing VB code. If the only hang-up is getting it to run as a service then they could save a lot of money if Visual Basic could, in fact, run reliably as a service.
You can write .NET services in any CLR language, including VB.NET --- your friend was thinking of VB6 and earlier.
(I do recall some fairly crazy kludges that allowed services to be written in VB6, but for all practical purposes, services written in VB6 weren't really a viable solution...)
There is no reason that Visual Basic .Net can't write a windows service. You can select a project which will create a windows service under the "Windows" projects in the Visual Basic section.
Writing a Windows Service in VB.NET (using any version of Visual Studio >= 2003) is just as effective as writing a Windows service in any other language.
Your friend may have been thinking of Visual Basic 6...or he's partial to another .NET language.
In either case...you should be fine to keep going on your path the way you are.
Your friend may be referring to Visual Basic, not VB.NET.
While VB.NET has syntax that is similar to Visual Basic and some convenience functions are still present, they are two entirely different languages and environments.
Your friend is correct in stating that Visual Basic (meaning 6 and earlier, not VB.NET) is a poor choice of a language for a service (or any new application), but VB.NET is every bit as legitimate as C# or any other CLR language.
It may be useful to refer to what you're learning as "VB.NET" or "Visual Basic .NET", rather than just "Visual Basic".
.NET certainly allows you to use Visual Basic to write a Windows Service. I believe there is even a default project template to do so. Here is an tutorial as such: http://www.vbdotnetheaven.com/UploadFile/mahesh/Winservvb11172005233242PM/Winservvb.aspx
All .NET code is converted to an intermediary language that is executed, thus all .NET languages can be used to write a windows service.