Is it possible to create XBAP applications with Expression Blend 3 only? - expression-blend

I want to create an XBAP application with blend, but when click on
File
New Project
it asks me if I want to create:
Silverlight 3 Application + Website --or--
WPF Application
Is there a way to create XBAPs from Expression Blend 3 or does this require Visual Studio?

Basically an XBAP page inherits from System.Windows.Controls.Page,so you create
public partial class Page1 : System.Windows.Controls.Page
So you should be able to create and design the page in Expression Blend,try WPF Application option.
For publishing you need Visual Studio....
http://blogs.msdn.com/maximelamure/archive/2007/01/24/create-your-own-pfx-file-for-clickonce.aspx http://www.xbap.org/faq.html
http://msdn.microsoft.com/en-us/visualc/aa700831.aspx
Or C# Express with extensions.

Related

Which Visual studio template to use for web-app. (Standard / MVC)

Having to select a template when creating a new project in Visual studio, which of the 2 should pick?("asp.net core web app" ...or... "asp.net core web app (model-view-controller)")
In order to try and discover the answer for myself, I'd have to create 2 different projects and compare the features and capabilities. If I knew what to look for, it might been easier.
if the on template is MVC, then what is the non-MVC actually then?
If I go for the one project, would I be able to convert to the other later then? (and vise versa)
The simplest explaination is: In asp.net core you work with web pages where each of the webpages (Razor pages) has a code behind file. In asp.net core web app (Model View Controller) your code behind is kind of centralised, in a controller file, and this code redirects to different view files. There is more to this than that. Furter explaination can be found on from page 12 of in this document: https://dotnet.microsoft.com/en-us/download/e-book/porting-aspnet-apps/pdf

Preventing Namespace expansion

While developing the designer keeps expanding the namespace. Where it should simply instantiate Class1, it is expanding the instantiation to Namespace.Class1.
Is there a way of preventing this behavior? Namespace is a multi-dotted default.
Your question is not clear enough, what platform/UI do your app use?
If you develop ASP.NET, the control/component is registered using register tag, but the file designer.vb or the designer.cs will still contain full namespace.
If you develop Windows Forms, the control/component will always have full namespace in the designer.vb and designer.cs.
If you develop WPF/Silverlight, the XAML file will directly display only the class name of the control you use, but the generated g.cs or g.vb will display complete/full namespace.
This is the default behavior of Visual Studio designer, whether ASP.NET, WPF/Silverlight, Windows Forms.
There's nothing you can do to change this, unless you created the UI WITHOUT designer support, such as creating a pure Window in WPF or Form in Windows Forms purely by code.

Sharepoint 2010 List and Visual Studio

as a newbie to Sharepoint.... I have created a simple list with several columns in Sharepoint 2010.
I now want to add a button on the List that I can programmatically add some onClick events to do the following:
get a handle on some of the columns in the list;
Distribute an email automatically based on the content of some of the columns
I am looking at using c# via Visual Studio 2010 for all the programmatic aspect of this development.
Is it possible to export the xml from Sharepoint 2010 then import into Visual Studio 2010 so that I can use the list I created as my starting point for the coding work? If so, how do I go about this?
Thanks.
You'll have to setup Visual Studio to work with Sharepoint.
Install it on a server that has Sharepoint 2010 running.
You can then create a webpart that incorporates the list (or a view on it) and add the button to that list.
But I imagine that you'll want to work on a specific row. So what you want is a Custom Action on that list (Visual Studio has a template for that: Add -> New Item -> Custom Action).
The Custom Action will create a new item in the Edit Control Block (the context menu that appears for every item in the list).
I prefer to create the ECB (Edit Control Block) menu items using JavaScript. In the page load I inject a jSon string that has additional information about each of the rows, and a JavaScript function then is called by the builtin SharePoint javaScript function that creates the ECB.
The JavaScript function you'll have to create is Custom_AddListMenuItems .
In that function you'll call CAMOpt to create menu items. If you want SharePoint to create the built-in menu items (and Custom Actions you created), set the return value of the Custom_AddListMenuItems function to true. (And fals if you don't want to see the built in ECB menu items and any Custom Actions you created)
You can start here:Jan Tielens Blogging's
Hope this helps.

Missing Scaffolding Options in ASP.NET MVC 3 Add Controller Dialog

I have downloaded and installed the release version of ASP.NET MVC 3 (File version: 1.13.113.0), Created a new project of type ASP.NET MVC 3 web application.
When I right click on Controllers folder=>Add Controller, The Add Controller dialog doesn't have any scaffolding option. It just contains a textbox for Controller name and a checkbox to add action methods for CRUD scenarios.
should I do anything to view the Scaffolding options (Template, Model Class, Data Context Class and View) in Add controller dialog box?
In the Web Platform Installer 3.0 you can find something called "ASP.NET MVC 3 Tools Update"
Install that one and you get the Scaffolding options and some other stuff.
Yes agreed it takes forever to install via web platform installer. Use link http://www.microsoft.com/download/en/details.aspx?id=1491 to download and install.
Make sure you have the lastest with the tool update.
http://www.asp.net/mvc
ASP.NET MVC 3 Tools Update can take a while, but it fixed it for me.
If you tell Web Platform Installer to update Visual Studio it will take basically forever, I had to force shutdown and try again just doing MVC 3.
Thanks Beijer.

Why does the default ASP.NET MVC 3 project not use controllers?

Upon creating a new ASP.NET MVC 3 Razor site, there are 9 Account\*.cshtml files which seem to be views with the controller logic inserted at the top of the view in an anonymous code block. There is no account controller class.
Why is this? As I understood, the benefit of MVC was the separation of concerns of code & presentation. Does this imply that I should remove all of the existing files & re-implement the Authentication & Authorisation layers?
It seems odd that MS would ship the 'worst possible example' with their flagship web framework.
Thanks,
Jarrod
Edit: I was using the wrong entry point within visual studio to create the application (see my comment below). Thanks!
Hmm, something is not quite right on your end.
I just created a new ASP.NET MVC3 Web Application.
I do have a 'Controllers' folder with a proper AccountController as part of the project.
Are you using Visual Studio?
This is incorrect. Here's the default folder structure in the MVC3 Razor starter app:
As you can see, there are two controllers in the ~/Controllers folder.
Just to be clear, I started a new VS2010 instance, created a new MVC3 project, selected "Internet Application" and Razor as the view engine.

Resources