What is the difference between DotNetNuke CMS and visualStudio . i mean, is it better to use DotNetNuke over VisualStudio for Asp.net web site development.
Visual Studio is used to build DotNetNuke. I would guess 98+% of all third party DotNetNuke coding (modules/provders/skins etc.) is done using Visual Studio.
If your purpose is to create a web site (e.g. organize the pages, and menus, add pictures, text, documents, manage users etc.) you can do all of that without writing any code by using DotNetNuke. With Visual Studio you must write code to do even the simplest thing like add a page with some text.
If you need to create some very custom web site features, or integrate with other software systems, then you will probably need to write some code. Pretty much any code that you write for platforms based on Microsoft's .Net technologies (including DotNetNuke) will be done using Visual Studio.
Dotnetnuke is a Content Management System done in ASP.Net Technology. Visual Studio is the editor used to write ASP.Net code. (basically .Net projects). Dotnetnuke is an ASP.Net project which can be opened and edited in Visual Studio. You can create your own project instead of using Dotnetnuke which is a precreated project.
dotnetnuke is more like joomla meaning its just a content management and visual studio is just an ide or editor.
you can develop your own DNN module using visual studio
Related
I'm looking for a new html/jquery/css IDE to edit and publish existing websites. Can I use Visual Studio Community 2015 to edit a website that doesn't use .NET and publish it to a server using ftp?
Yes you can use Visual Studio as your main editor. Select any ASP.NET project as your starting point, delete everything in the project and you're good to go. You can add a Publish Profile to enable web deployment (which supports FTP).
It will require the concept of a "Project File" for most features to work well. There is the old Web Site project which just works on any folder, but that hasn't seen much love in the past years. It's new cousin is being introduced with Visual Studio 15 (which will likely be Visual Studio 2016 or 2017).
As an alternative you may want to look at Visual Studio Code as well, it's the light weight cousin of Visual Studio Community Edition and is suited perfectly for the kind of work you're planning it seems.
I have got 4 components of visual studio 2010 express
1)MS Visual Basic 2010 express
2)MS Visual C#
3)MS Visual basic
4)MS Visual Web Devoloper.
But none of them provide me Web part templates for sharepoint 2010. Which one would I need for this?
Do I need a proffessional? or even a Visual studio 12?
It looks like you need to have Visual Studio and SharePoint installed on the same machine in order to develop for SharePoint:
Chris Hopkins' Blog
I can tell you from personal experience this is true. I've always had to install Visual Studio onto a SharePoint server when I wanted to write new solutions for SharePoint.
If you are simply trying to edit a page layout or master page, or some other static type of content in SharePoint, you can use many tools to do so. I've successfully edited things with NotePad++ from my client PC. As long as you have the permission for the library where those things are kept, you can make changes.
I originally thought you meant developing SharePoint SOLUTIONS, by which I mean additional back-end functionality, site features, and the like.
I've been given the task of developing some extensions for Visual Studio for our internal use. These will have to support a couple of different versions of Visual Studio (VS2008, 2010 and 2012 - VS2005 would be a nice to have but not essential). I'd like to develop these in as consistent a way as possible, reusing as much of the code as possible, while fitting it into the existing project structure for these kinds of tools, which is a Visual Studio 2012 .sln.
What's the best / easiest way of developing this kind of extension? A VSPackage project? Can I make a 2008-compatible VSPackage which is developed in VS2012?
The features I will need for the extensions I'm writing at the moment are pretty basic - I need to create Tools menu commands, possibly a custom toolwindow. My requirements might change later on but I don't need editor adornments or anything like that at the moment.
I saw this question which might seem to be a duplicate, but the answer which was accepted doesn't answer the question, so...
It really depends on what is your extension going to do.
VS2008 does not support extensions (.vsix) and you will need to write VSPackage deployed as msi for it. You also won't have access to many new features introduced in VS2010 (easier editor integration and access to vs services via MEF), but basic stuff such as manipulating solution/project/files should be fine and work on all versions (e.g. using DTE should be ok).
As far as I remember for VS2008 you will also need to obtain a PLK, which is no longer required for 2010 and 2012.
I haven't tried developing 2008 package in VS2012, but you definitely can develop 2010 extension in 2012.
Also remember that VS2008 is .Net 3.5, so your code should use .net 3.5 and version of c# which it supports to be portable.
We would like to automate the upload of Visual Studio Extensions that we have written to the Visual Studio Gallery.
We currently use a combination of CruiseControl.Net, Msbuild files and Powershell scripts to automate the deployment of all the bits and pieces of our framework.
However we would like to automate the deployment of the development tools that we have created to the Visual Studio Gallery.
These tools are built using Visual Studio 2012.
Thanks for any helpful advice or pointers.
It's possible to do this with Canopy and FAKE. I just did it in https://github.com/fsprojects/Paket.VisualStudio/blob/master/build.fsx#L177
Unfortunately there is no good way to do this. There is no publicly exposed API for uploading extensions. The only way I'm aware of is to create an instance of a web browser and simply automate the process of filling out the forms and navigating through the menus.
I have been given control of a web site in Classic ASP. What is the best way to manage this code with VS 2010? More specifically, how can I best import it into VS 2010. Should I start with a blank solution? A blank ASP.NET project? Obviously I'm expecting it to run through a build process, but I would still want to create it in a way so that I can edit the files with VS 2010 and run it on my debugging web server when needed for testing.
If i'm not wrong, you can't run a classic asp website trough a build process.
In visual studio 2010 you can only open the file and edit them as a file editor. But there's not a lot of interaction between classoc asp and vs2010
Also : read this it'll help you - Create classic asp project in Visual Studio 2010 from scratch