Can anybody recommend a "starter kit" or basic framework for an asp.net web app that can read data from Microsoft Dynamics CRM?
No updates are required from the app at this time, just reads. I'm currently reading through the SDK documentation but a simplified project would be quite handy.
Some sample code (in C# and VB.net) for doing various things with CRM comes with the SDK.
Have a look in the \sdk\server folder and the \sdk\visualstudiotemplates folder in the same folder that you installed the SDK in. Hopefully these should give you a head start.
As for Microsoft Dynamics CRM 2011 Software Development Kit (SDK) the download can be made here
In the /sdk/crmsdk2011.chm document one should find many tutorials that are assisted by code (.sln included)
Related
I created a ASP.net MVC 5 project in Visual Studio 2013, running in a Windows 8.1 Pro.
I've been ask to put my project on a SharePoint, but I don't quite know how it's done.
i tried creating a SharePoint project on my Visual Studio but it won't let me since I don't have SharePoint installed, and when I try to install SharePoint Foundation 2010 or 2013 it complains I don't have Windows Server.
How do I make my project work on a SharePoint?
So you want to put your project on sharepoint? Cool!
In your case you definetly want to get your own SharePoint environment. To develop Apps (or Add-ins as they are called today) you mainly use Client-side code and techniques. This also means that you need to handle the SharePoint resources with asyncronous programming. Its very powerful, But that is not what you are asking for.
I would set up an SharePoint 2013 Foundation environment since its free and will very much deliver the capabilities you are after. Keep in mind though that SharePoint is a HUGE system that requires some understanding to be utilized.
I made a blogpost a while back where i Installed Win Server 2012 R2 on a external disk, this example works with SharePoint if you just want to debug your project on a SharePoint server. Check it out here: http://bayerlein.se/install-windows-server-on-external-hdd-with-the-help-of-virtual-box/
This solution will of course also require that you install your development program in the same environment.
Good luck//Kodz
It really depends upon what you want to do. Do you need to create a provider hosted app with MVC for SharePoint 2013? In that case, you might succeed with including the necessary references and tooling code (but you still might lack the app manifest project). Technically your project won't run on SharePoint but uses the SharePoint API.
If you need to create an SharePoint solution package, you need a SharePoint development install (and as SharePoint doesn't install on all client OS, your best way is going virtual with a SharePoint development VM). Keep in mind that developing solution packages is a different kind of trade than developing for MVC, so start with a Pluralsite course or some other kind of training.
I think you can create a SharePoint app. You can use VS2015 with SP online so that you don't need to install SP locally. Create a trial o365 account and enable developer site on it. You can deploy your app on the developer site then. If you have developer site from you client instead of using sp online you can use that too.
Once your app works you can create package to deploy on the SharePoint environment.
I think right now, the best way for you would be signing up as Microsoft Office 365 Developer and having a trial of the 365 cloud where you can setup sharepoint 2013 site collection and also develop apps using their tool NAPA.
These days they are calling apps "SharePoint Add-ins"
NAPA and SharePoint Add-ins
I would also suggest you take a look at this article:
SharePoint 2013 Developing Apps vs. Solutions
I have been developing ASP.NET websites solo but now I have 2 more developer and I want a tool to share project with them to create a team development environment but I don't want to share my source code with them for example my App_Code folder. I am using Visual Studio 2013 Ultimate Edition for development.
In other words i need an environment where i can share my project with other developers without my App_Code folder files.
Sorry for my bad English.
Create a class library Project and add your sources to it.
Build it in release mode.
Add reference to the output DLL from the main project.
That's about it.
Regarding Source-Control Tools or TFS - it is good to have but will not replace the solution provided and is not focused to provide a solution to your problem.
It just a way to ease team development regarding versioning, bug tracking and etc..
I want to load test an ASP.NET web service. I have Visual Studio 2008 Professional Edition and Visual Studio 2010.
Can either one of these products facilitate load testing? I can't seem to find anything and all Google returns is higher end editions of Visual Studio.
If not, what are some of the alternatives.
Or better yet, is there a product where I can feed it an IIS log and it will essentially replay it?
There is a free Microsoft load testing tool called WCAT. It is a command-line HTTP load generator that replays a test case script. To avoid creating the script manually, you can record your test case in Fiddler and then generate scrip using WCAT Fiddler Extension. This blog has a step-by-step instruction, which I tested, and it works.
On your question about replaying IIS log: check this source. It outlines how to generate WCAT script by querying IIS log using Log Parser. I did not test it though.
Is there a cheaper way to do load testing than upgrading to Visual Studio 2010 Ultimate
and also there was a tool called "MICROSOFT WEB APPLICATION STRESS TOOL" but i couldnt find its download apperantely MS removed it from its official page. check this forum for download link http://forums.iis.net/t/1161284.aspx for usage http://www.west-wind.com/presentations/webstress/webstress.htm
The Microsoft Visual Studio Team System 2008 Test Edition would also give you access to these tools. Unfortunately neither of the tools you mention include any load testing capability.
You may be able to get your licence for 2008 Professional edition changed to Test, but I doubt it now.
Here are a couple of other questions with answers that may help choose a tool.
stress-and-performance-test-on-asp-net-app
best-tool-for-performance-testing-asp-net
how-to-set-up-a-load-stress-test-for-a-web-site
I am looking for ASP.NET applications that I can deploy to my local server. Can anyone suggest a link for open source .NET applications or any book?
Any suggestion would be helpful.
Thanks
If you are using Visual Studio 08 or 10 then they have built in ASP.NET Application Templates which will get you started.
These include a basic website with a Home and About page, also a Login/Register page and all the code to handle the Login and Registration.
If you create one of these, then you can deploy it to a local server as long as you have the .net framework, IIS and various other bits installed.
EDITS
Go and download the Web Platform Installer. From here you can download various templates and up-to-date tools. I would upgrade from VS 05 to a newer version, maybe Visual Web Developer Express 2010 as this will give you more options.
I've recently started playing around with ASP.NET and I was just about to connect to a database using LINQ, when I realised that you have to change a bunch of stuff in the project first if you created a normal web site project in Visual Studio 2008.
All the information about LINQed projects in VS2008 that I have found start directly from scratch with a completely new web site. What modifications do I have to make to my project to be able to make use of LINQ?
I think that your question can be answered by viewing this post on stackoverflow.com.
In short your application will need to have access to System.Linq which comes from the .NET 3.5 framework. If your application is currently using .NET 2.0, it is possible to hack a setup with the CTP packages for Linq prior to it being released with Visual Studio 2008, but you might find it hard when you push your application out to production to a hosting company because you will have to install .dll's into areas you generally don't have access too.
Good luck on your conversion to Linq.