Why can't I add a XML datasource in Expression Blend 3? - expression-blend

I'm using Expression Blend 3
I click on "add live datasource", "add new xml datasource"
copy in a URL
but the OK button remains blank
adding a local XML datasource file works fine
How can I add a URL datasource in expression blend 3?
does this work for anyone else?
The problem is on every Expression Blend 3 I install on any computer, seems to simple be turned off in the beta.
alt text http://tanguay.info/web/external/blenddataokbutton.png

I just tried using blend 1.0. This version also had other options, such as 'infer xml schema'.
My guess is that there was some check added in later version to ensure that the file pointed to has an extension.
My suggestion is to edit the xaml directly. Note, this is old XAML from blend 1.0:
<Window.Resources>
<XmlDataProvider x:Key="rssDS" d:IsDataSource="True" Source="http://www.tanguay.info/web/rss/"/>
</Window.Resources>
Hope that helps, let me know.

I ran into the same problem when I tried to reimport a sample data from an XML file. The data source already exists or at least Blend thinks it still exists. You should see a warning if you mouse-over the Data Source Name textbox.
Delete the data source from the Data tab.
Delete the folder in the project view.
Rebuild the project.
If that doesn't clear it out, restart Blend.
That's what I had to do. I have Expression 4.0 Ultimate.

Related

The type or namespace name 'DotNetNuke' could not be found

I built a custom theme for DNN several months ago using the Christoc templates for Visual Studio. I needed to make a small HTML adjustment today so I re-opened the solution and made the change but when I rebuilt the project, I get several build errors, presumably because it no longer recognizes my DNN dll:
The type or namespace name 'DotNetNuke' could not be found (are you missing a using directive or an assembly reference?)
I checked my C:\path_to\dnndev.me\bin\DotNetNuke.dll and it's still there so I'm not sure why Visual Studio isn't seeing it.
When I built the skin originally, I was running DNN 9.1.1 but have since upgraded to 9.3.2. Could that be causing my issue?
I read elsewhere that I could be building on the incorrect version of .NET framework but I don't know what version to use for DNN 9.3.2 so I tried several different version with no change in results.
How can I solve this issue?
UPDATE:
Per the answer here, I rebuilt with .NET 4.7.2 and it did not solve my issue.
UPDATE 2:
Okay, so the small change I made was adding another layout page like the Home.ascx and Edit.ascx files that come with the template. If I remove the new layout files, the project builds fine.
What could I be doing wrong when adding a new layout?
What you read about the .Net framework version is correct. You need to 4.7.2.
The problem was a new layout I had created. I right clicked on the project and selected Add > New Item and chose Web Forms User Control. This was the wrong way to add a new layout.
I successfully added it by copy/pasting one of the template's pre-existing layouts and renaming it. The project builds fine now.
Ah, now I understand what went wrong. Adding a Web (Forms) User Control is not completely wrong, as a skin (or theme) is a kind of Web User Control, and has the same extension (.ascx).
What you have to do is deleting the code behind file (.ascx.vb or .ascx.cs), and change the first line of the ascx file to
<%# Control language="vb" AutoEventWireup="false" Explicit="True" Inherits="DotNetNuke.UI.Skins.Skin" %>
(But copying another skin file is also a good solution as propably you have most of the references to the skin object already there)

Tiny MCE v2.1 code editor

Call me old fashioned, but there is nothing I can do but only to use the old version of Tiny MCE, which is 2.1.
So, what I'm trying to do is to add a "download" attribute to tag, after I open HTML editor I type this attribute, when saving it simply disappears. There is no official documentation to this old version on the official site. The new ones doesn't mention anything about this feature at all. overall editor look. code editor look
Also, I tried to add "download" in the extended valid elements configuration:
extended_valid_elements: "code[class|dir ,however no success as well.
Did anyone by any chance faced the same problem?
Could use a little bit of help.
Well, if anyone ever encounters the same problem, which I highly doubt, you would need to open tiny_mce.js file, and on the line 1928 there will be "A : "id|class|style|title|download" ", this is the place, where I added "download". Afterwards I was able to add this attribute in the HTML code editor.

Error in parsing StoryBoard in Xamarin.iOS

I am developing an application in Xamarin.iOS. But after three days of work, Xamarin cannot render the Main.StoryBoard and gives the following error:
There was an error in Parsing the XML in this document
and a long list of logs.
Any idea how to revert to or something like this
#Xhulio ran into this before. Try opening it with Xcode first to see if it works. If not you can try opening the storyboard with an XML editor (I used Notepadd++ with an XML plugin), then identify and correct the invalid XML. If you are using source control you can try comparing your changes to identify the issue. Hope this helps.

Prevent VS2010 CSS Validation from Reverting to CSS 2.1

I validate CSS in my new projects against CSS 3.0, thanks to the solution here:
VS2010, HTML 5 and CSS 3 Validation
However, every time I load the project, CSS validation reverts to 2.1 and has to be set through the toolbar to validate against 3.0 again.
Is there a way to make my selection sticky?
You can set it in Options -> Text Editor -> CSS Validation. I have taken the screenshot from VS2012. It is same in VS2010.
First, shut down VS2010
Assuming you're validating against html5 - the validation option is in
Text Editor-->HTML-->Validation
Set it to HTML5 validation. Then verify the following file exists:
< your install directory >\Microsoft Visual Studio
10.0\Common7\Packages\schemas\html\html_5.xsd
Copy the file elsewhere to be safe then edit the original file using a text editor. Near the top of the file find the string:
vs:cssschema="CSS 2.1"
and change it to:
vs:cssschema="CSS 3.0"
if it isn't already. Then save the file and restart VS2010. That should take care of making CSS 3.0 validation sticky against html5 projects

WP7 - Not picking up embedded fonts

I have been trying to use some custom fonts within my WP7 app.
I followed the example as per http://www.jeffblankenburg.com/2010/10/24/31-days-of-windows-phone-day-24-embedding-fonts/ but in my project it simply will not pick up the custom font.
I have downloaded the sample project in this example and this one does work okay.
So, I have now used the same font used in there, and included in my project. I have ensured that the properties on the file are identical (Build Action = 'Content' and Copy To Output Directory = "Always")
I have used in my XAML in exactly the same way i.e.
FontFamily="Fonts/DigitalDream.ttf#Digital Dream" FontSize="24"
But to no avail. The custom font is just ignored. Is there something that I am missing, or a setting .. anything that would allow this to work in one project, but not another?
I have discovered that it will work if my XAML page is defined at the root level, i.e. immediately under the project, but in my case I have it in a 'Views' folder.
My understanding was that
FontFamily="/Fonts/DigitalDream.ttf#Digital Dream" FontSize="24"
should start at the root folder of the project?
thanks
Custom fonts can be a little tricky. I spent several hours once trying to embed an .otf font only to find that it just didn't seem to be doable.
You're on the right track, though. A .ttf font should be embedable. It's hard to get the right combination of paths and filenames to make the font work, though.
The easiest way I've found to handle some of these more difficult "magic string" type of situations in XAML is to let Expression Blend do the heavy lifting.
Here's a blog post about using Blend to embed fonts. The nice thing about using Blend is that it gives you some visual indications that things are set up correctly--i.e. you can see the font you want in the font selection menu. This is what finally clued me in on the .otf issue. I couldn't see the font in Blend.
And here's an example of a custom font that I've used in one of my apps:
<TextBlock Name="MyTextblock"
FontFamily="/MyAppName;component/fonts/Fonts.zip#Segoe UI Mono">
That's FontFamily URI is a pain to get right. I'm pretty sure that's your problem.
I was actually having the same problem. I followed everything to the dot and still I wasn't able to embed one particular font. So I created a new project and tried embedding the font there. Still no luck. I then tried embedding some other font. And lo and behold, as soon as I typed the FontFamily attribute, I could see that it had embedded. This was particularly odd since I didn't have to change any properties of the font.
I opened the project in Blend and clicked on the font property box to the right. It took a few seconds and then it embedded the font I was having problems with in the first place.

Resources