Comments by DannyStaten

DannyStaten 19-Sep-15 10:53am View

I don't have that solution readily available any more. If I am understanding my old post, I would suspect that it I changed the " simply to the literal single quote. So I am guessing it looks like this:
string connection = String.Format("metadata=res://*/MyData.csdl|res://*/MyData.ssdl|res://*/MyData.msl;provider=System.Data.SQLite;provider connection string='data source={0}'", file);
_data = new MyDataEntities(connection);

DannyStaten 3-Sep-11 9:25am View

my problem is that what you have suggested here is not working... I did notice at least that it doesn't show the undesired message until the textbox loses focus, so it isn't as critical.

DannyStaten 11-Aug-11 0:54am View

Thanks, all my google searches found other things that weren't nearly as direct and useful.

DannyStaten 28-Jul-11 22:55pm View

So I have done that. I even went so far as to directly copy the class that the productivity tool generated and then do very small tweaks to run the code on my generated document.

The end result is a .docx package that is a lot closer the next time I do a comparison of the files, but there are still pretty significant differences, and Open Office still won't open the file.

Some of the differences include:
In app.xml my document has all node names with ap:NodeName (e.g. <ap:temlate>) and the one that opens in Open Office has just the straight up node name.

theme.xml in my document is theme1.xml.
All my documents xml don't have standalone="yes" in the xml document node. File that ran through MS Word have standaloen="yes"

My documents have encoding in lowercase "utf-8" MS Word's file has caps "UTF-8".

Some of the relationships are in different orders in some files.

As I said, it gets the file a lot closer, but there are still things that the code generates that will not play nicely with Office. Seems quite frustrating.

DannyStaten 23-Jul-11 23:19pm View

Yeah I am familiar with the productivity tool and it had saved me a lot of grief in the past. I hadn't realized it had the tool to compare files. That will definitely get me pointed in the right direction. Thanks

DannyStaten 23-May-11 23:22pm View

So it is really strange. I created a new mvc application and made it an exact copy of the one that would not publish. The newly created and spun up project published and ran without a hitch. I had already done the things that you were kind enough to give me as tips, so in my odd world it was something else. That being said, I do appreciate you posting a great answer, and one that is likely to answer 99.9% of the people's needs should they find this thread in their searches for help. Thanks for answering.

DannyStaten 22-May-11 14:44pm View

I have already verified several times that my godaddy hosting is running IIS 7.0 and .net 4. I also have checked the bin and I have local copies of all the dlls that their articles mention (IE Microsift.Infrastructure, System.Web.Razor etc etc). I will have to check that one more time because EVERYTHING I can find seems to say that just getting the right dlls in your bin should make everything work.

Before I updated my bin, I would get an error that the dependencies in my web.config couldn't be found. So I wonder if I am missing a namespace in my web.config which is causing the code to not know where to find ViewBag. If that were the case though, it should not work locally... grumble.

DannyStaten 16-Apr-11 14:51pm View

Wow thanks for the fresh pair of eyes there.

DannyStaten 16-Apr-11 14:45pm View

LOL thanks. Count that one up as a brain fart that I just needed a fresh pair of eyes on. Thanks

DannyStaten 2-Apr-11 9:44am View

Cool thanks for sharing that information.

DannyStaten 30-Mar-11 22:45pm View

So I found something that lets me do what I was trying for, and may be something you were assuming I was already doing. A blog post here http://www.labo-dotnet.com/post/Create-Word-document-using-the-OpenXML-20-SDK.aspx shows how to pull a style definition from an existing document, include it in your project and then load that styles.xml in as the styles part for your programatically created docx. It saves me the trouble of having to define my styles programatically, and once I have done that, the styles do work as they are applied. A note to any who do that: You must extract the styles you want from a document that uses them explicitly in it's contents or the styles.xml won't define that style.

DannyStaten 30-Mar-11 21:55pm View

So far I have been trying what you are suggesting and it isn't doing anything.

Paragraph chapterHeader = new Paragraph(new Run(new Text(chapter.Name)));
ParagraphProperties props = new ParagraphProperties();
ParagraphStyleId pStyle = new ParagraphStyleId() { Val = "Title" };
props.Append(pStyle);
chapterHeader.PrependChild(props);
buildingBody.Append(chapterHeader);

That is resulting in xml that appears identical, but when I open my word document there is no style applied.

I am not assigning the rsids on my paragraphs. I guess I don't yet understand their purpose, but that wouldn't be part of what the current problem is I assume.

DannyStaten 30-Mar-11 10:14am View

Thanks. I am generating my style completely in code so this should be perfect. I will be sure to give it a try as soon as I get home from work being that this is a personal project I am doing on the side 8).

Comments by DannyStaten (Top 13 by date)