We’re continuing to improve upon the power and productivity of Visual Studio, making it easier to use, no matter what platform you’re on, no matter what app you’re building. We also want to make it easier for you to choose which edition of Visual Studio is the right one for you. Last November, we made Visual Studio Community 2013 available, our free, full featured and extensible IDE for non-enterprise application development. Today, we’re announcing the editions of Visual Studio 2015 that will be available when we release the final product this summer.
I’m excited to share that we’re bringing the value
we deliver in Visual Studio Premium and Visual Studio Ultimate into one single offering called Visual Studio Enterprise with MSDN. It includes all the high value features you’re already familiar with in Visual Studio Ultimate, along with new innovation that’s coming with the 2015 release. So, in addition to Visual Studio Community and Visual Studio Professional with MSDN, our new Visual Studio Enterprise with MSDN rounds out the three primary Visual Studio 2015 offerings.
We’ll continue to offer Visual Studio Professional, Team Foundation Server, Team Foundation Server Express, Visual Studio Express and MSDN Platforms as a part of the complete...(Read whole news on source site)
Microsoft's coming Surface 3, an Intel Atom x7-based Surface, is the new little sister to the Surface Pro 3.
I’m very excited today to see the launch of StaffPad, a groundbreaking music notation application from the UK which features advanced handwriting recognition that allows you to write music naturally with a pen and play it back in high fidelity. You need...(read more
In my previous post
, I showed a pretty trivial index and asked how to efficiently update it. Efficient being time & memory wise. The easiest approach to do that is by using a reverse lookup option. Of course, that means that we actually need to store about twice as much data as before. Given the following documents: users/21 – Oren Eini users/42 – Hibernating Rhinos users/13 – Arava Eini Previously, we had: Term Documents
Oren users/21, Eini
width="200">users/21, users/13 Hibernating users/42, Rhinos users/42, Arava users/13 And with the reverse lookup, we have: Term Documents Document Terms Oren users/21, users/21 Oren, Eini Eini users/21, users/13 users/42 Hibernating, Rhinos Hibernating users/42
Update: I got distracted while titling today’s edition and mistakenly labled it as 1830 when it should have been 1831 – thanks to Paweł Niedbała for letting me know via the comments Software A Preview of WinJS 4.0 – The Windows Apps Team announce the preview release of WinJS 4.0 the latest version pof their […]
According to multiple requests, we’ve made up a tutorial that explains how you can manage visibility of reserved time spans for different users in one appointment calendar in ASP.NET.
The idea is the following: if one user adds an event to the calendar, another user of this calendar is not able to see this event details, only a marked timespan, as it is demonstrated on the picture below:
The tutorial is created in ASP.NET MVC5 Razor. You can download a ready ASP.NET calendar control example with blocked timespans right now, or follow the instructions described below:
We’ll create an MVC project
in MS Visual Studio 2013, install DHTMLX Scheduler .NET and then add the requested marked timespans functionality.
1.Creating a New MVC Project
We’ll start from creation of a completely new project, naming it according to our topic - LoadMarkedTimespans. In the left panel of VS select Web and then ASP.NET Web Application. In the New ASP.NET Project window select MVC and make sure that authorization option is set as ‘Individual User Accounts’.
It’s going to be a project with ASP.NET Identity based authorization and a bunch of controllers and views to manage user actions.
2. Database Initialization
Afterwards, we need to initialize the database, create...(Read whole news on source site)
You can learn a lot by trying new things. Over the past 18 months I have been switching IDEs and editors every few months going between Atom, Visual Studio, Brackets, WebStorm, and Sublime … and then back again. This has given me an appreciation of the various tools, all of which have their pros. For most of that time I have been living in OSX and lately I’m loving Brackets. Brackets is lightweight, browser-based, and has a great extension model. I feel very productive in it and can run fast and hard when I get a coding itch I need
It’s Tuesday again and I came with top news of the week floating around Microsoft Platform. In this top news post, composing links on Azure, Windows 10, Node.js and Microsoft Band. Hopefully, you will love to read those. Share your views on the posts those I share over this Microsoft Tuesday
channel and engage me to provide more in coming days. Announcing the availability of Azure App Service
In a mobile-first, cloud-first world, companies are using apps to connect with and better engage their customers, partners, and employees anywhere, and on
any device. They are relying on developers to build those apps with increasing speed –that can connect to popular services and on-premises systems and auto scale as the business needs. Today, I’m excited to announce Azure App Service, a unique new service which helps developers deliver cross-platform, cloud-connected apps faster than ever before. Scott Guthrie Announces Azure for Students through Microsoft Imagine
Announcing free Azure web development services for verified students – no credit card required! Microsoft Imagine helps students of all ages learn to code and build their skills with free software and online...(Read whole news on source site)
Azure API Tools for Visual Studio 2013 gives developers a quick path to connecting to third-party REST APIs.
SharePoint, being a content management system, of course, offers a couple of ways to query its contents programmatically. Here we will explore some of these options.
First, of course, there are the web parts. These allow us to configure queries visually on a page. The most important web parts are:
: use this for simple queries that do not return much contents, on a single site collection. Can be used in SharePoint Online. Can only be customized through XSLT.
(introduced in SharePoint 2013): more powerful, but does not exist in SharePoint Online. Can handle more complex queries
: can be used to view of a specific list. The display can be totally configured. XsltListViewWebPart
is a bit more powerful.
: requires that you pass an SPList
and a SPQuery
instance. Can only display pre-defined views.
There are several APIs for querying, either directly or using the search index.
: can only be applied to a single list: