L
ljh
Google ran dry on me while looking for .Net examples of how to compare 2
Word Docs.
Has anyone here seen anything like that?
Word Docs.
Has anyone here seen anything like that?
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
L
Lloyd Dupont
what would you like to compare?
the file size? => System.IO
the binary content? => System.IO
the rich text content? => http://msdn2.microsoft.com/en-us/ms186213.aspx
the file size? => System.IO
the binary content? => System.IO
the rich text content? => http://msdn2.microsoft.com/en-us/ms186213.aspx
L
ljh
This may be moot at this point......
After I read the "Granting and Removing Permissions for an Office Solution"
thing, there's simply no way an end user would EVER do this to grant
permissions for an Office solution.
I hope like hell that I misunderstood something. Do they really expect end
users to ...
1.. Open Microsoft .NET Framework 2.0 Configuration again.
2.. Right-click the VSTOProjects node, and then click New on the shortcut
menu.
3.. Enter the name Security Test Strong Name for the new code group, and
then click Next.
4.. In the Choose the condition type for this code group list, click
Strong Name.
5.. Click Import.
6.. Browse to C:\Walkthroughs\My Security Test\My Security Test\bin\My
Security Test.dll for Visual Basic or C:\Walkthroughs\My Security Test\My
Security Test\bin\debug\My Security Test.dll for C#, and then click Open.
7.. Click Next.
8.. Click Next to accept the FullTrust permission set, and then click
Finish.
9.. Close Microsoft .NET Framework 2.0 Configuration.
My users are damned lucky to understand how a mouse works. They'll never
get this.
If I haven't misunderstood something, this really sucks for developing
Office solutions in .Net. It just won't happen.
After I read the "Granting and Removing Permissions for an Office Solution"
thing, there's simply no way an end user would EVER do this to grant
permissions for an Office solution.
I hope like hell that I misunderstood something. Do they really expect end
users to ...
1.. Open Microsoft .NET Framework 2.0 Configuration again.
2.. Right-click the VSTOProjects node, and then click New on the shortcut
menu.
3.. Enter the name Security Test Strong Name for the new code group, and
then click Next.
4.. In the Choose the condition type for this code group list, click
Strong Name.
5.. Click Import.
6.. Browse to C:\Walkthroughs\My Security Test\My Security Test\bin\My
Security Test.dll for Visual Basic or C:\Walkthroughs\My Security Test\My
Security Test\bin\debug\My Security Test.dll for C#, and then click Open.
7.. Click Next.
8.. Click Next to accept the FullTrust permission set, and then click
Finish.
9.. Close Microsoft .NET Framework 2.0 Configuration.
My users are damned lucky to understand how a mouse works. They'll never
get this.
If I haven't misunderstood something, this really sucks for developing
Office solutions in .Net. It just won't happen.
L
Lloyd Dupont
If I haven't misunderstood something, this really sucks for developing
But for what I have understood from what I have read about it, it's just for
big corporation who have in-house developer developing in-house solution.
Company like insurance, bank, fortune 500, etc....
Well I don't know much about it. Neer done it myself.Office solutions in .Net. It just won't happen.
But for what I have understood from what I have read about it, it's just for
big corporation who have in-house developer developing in-house solution.
Company like insurance, bank, fortune 500, etc....
K
Ken Cox [Microsoft MVP]
You'd probably want a setup routine to make the changes using caspol.
Anyway, I'm with you that VSTO has problem when it comes to real-world
usage:
http://weblogs.asp.net/kencox/archi...tment-with-VSTO-2005-Internet-Deployment.aspx
Ken
Microsoft MVP [ASP.NET]
Anyway, I'm with you that VSTO has problem when it comes to real-world
usage:
http://weblogs.asp.net/kencox/archi...tment-with-VSTO-2005-Internet-Deployment.aspx
Ken
Microsoft MVP [ASP.NET]
L
ljh
Thanks for the link!
It really does sucj because I LOVE Office. Open Office doesn't begin to
offer the slick UI and feature set that MS Office does.
I am considering writing a COM Addin with VB6....although I hate the idea of
splitting up my development between VB6 and VB.Net - especially while I am
trying to add C++ to my skillset.
It really does sucj because I LOVE Office. Open Office doesn't begin to
offer the slick UI and feature set that MS Office does.
I am considering writing a COM Addin with VB6....although I hate the idea of
splitting up my development between VB6 and VB.Net - especially while I am
trying to add C++ to my skillset.
Ken Cox said:You'd probably want a setup routine to make the changes using caspol.
Anyway, I'm with you that VSTO has problem when it comes to real-world
usage:
http://weblogs.asp.net/kencox/archi...tment-with-VSTO-2005-Internet-Deployment.aspx
Ken
Microsoft MVP [ASP.NET]
ljh said:This may be moot at this point......
After I read the "Granting and Removing Permissions for an Office
Solution" thing, there's simply no way an end user would EVER do this to
grant permissions for an Office solution.
I hope like hell that I misunderstood something. Do they really expect
end users to ...
1.. Open Microsoft .NET Framework 2.0 Configuration again.
2.. Right-click the VSTOProjects node, and then click New on the
shortcut menu.
3.. Enter the name Security Test Strong Name for the new code group, and
then click Next.
4.. In the Choose the condition type for this code group list, click
Strong Name.
5.. Click Import.
6.. Browse to C:\Walkthroughs\My Security Test\My Security Test\bin\My
Security Test.dll for Visual Basic or C:\Walkthroughs\My Security Test\My
Security Test\bin\debug\My Security Test.dll for C#, and then click Open.
7.. Click Next.
8.. Click Next to accept the FullTrust permission set, and then click
Finish.
9.. Close Microsoft .NET Framework 2.0 Configuration.
My users are damned lucky to understand how a mouse works. They'll
never get this.
If I haven't misunderstood something, this really sucks for developing
Office solutions in .Net. It just won't happen.
L
ljh
Is this mitigated if the user installs the AddIn with an MSI installer?
Would it have full trust then without asking users to tweak .Net
configurations?
Would it have full trust then without asking users to tweak .Net
configurations?
Ken Cox said:You'd probably want a setup routine to make the changes using caspol.
Anyway, I'm with you that VSTO has problem when it comes to real-world
usage:
http://weblogs.asp.net/kencox/archi...tment-with-VSTO-2005-Internet-Deployment.aspx
Ken
Microsoft MVP [ASP.NET]
ljh said:This may be moot at this point......
After I read the "Granting and Removing Permissions for an Office
Solution" thing, there's simply no way an end user would EVER do this to
grant permissions for an Office solution.
I hope like hell that I misunderstood something. Do they really expect
end users to ...
1.. Open Microsoft .NET Framework 2.0 Configuration again.
2.. Right-click the VSTOProjects node, and then click New on the
shortcut menu.
3.. Enter the name Security Test Strong Name for the new code group, and
then click Next.
4.. In the Choose the condition type for this code group list, click
Strong Name.
5.. Click Import.
6.. Browse to C:\Walkthroughs\My Security Test\My Security Test\bin\My
Security Test.dll for Visual Basic or C:\Walkthroughs\My Security Test\My
Security Test\bin\debug\My Security Test.dll for C#, and then click Open.
7.. Click Next.
8.. Click Next to accept the FullTrust permission set, and then click
Finish.
9.. Close Microsoft .NET Framework 2.0 Configuration.
My users are damned lucky to understand how a mouse works. They'll
never get this.
If I haven't misunderstood something, this really sucks for developing
Office solutions in .Net. It just won't happen.
L
ljh
FYI...
You may also want to see the "Why use the PIAs?" thread in the
microsoft.public.office.developer.com.add_ins ng.
You may also want to see the "Why use the PIAs?" thread in the
microsoft.public.office.developer.com.add_ins ng.
Ken Cox said:You'd probably want a setup routine to make the changes using caspol.
Anyway, I'm with you that VSTO has problem when it comes to real-world
usage:
http://weblogs.asp.net/kencox/archi...tment-with-VSTO-2005-Internet-Deployment.aspx
Ken
Microsoft MVP [ASP.NET]
ljh said:This may be moot at this point......
After I read the "Granting and Removing Permissions for an Office
Solution" thing, there's simply no way an end user would EVER do this to
grant permissions for an Office solution.
I hope like hell that I misunderstood something. Do they really expect
end users to ...
1.. Open Microsoft .NET Framework 2.0 Configuration again.
2.. Right-click the VSTOProjects node, and then click New on the
shortcut menu.
3.. Enter the name Security Test Strong Name for the new code group, and
then click Next.
4.. In the Choose the condition type for this code group list, click
Strong Name.
5.. Click Import.
6.. Browse to C:\Walkthroughs\My Security Test\My Security Test\bin\My
Security Test.dll for Visual Basic or C:\Walkthroughs\My Security Test\My
Security Test\bin\debug\My Security Test.dll for C#, and then click Open.
7.. Click Next.
8.. Click Next to accept the FullTrust permission set, and then click
Finish.
9.. Close Microsoft .NET Framework 2.0 Configuration.
My users are damned lucky to understand how a mouse works. They'll
never get this.
If I haven't misunderstood something, this really sucks for developing
Office solutions in .Net. It just won't happen.
L
ljh
Ken,
Awesome link to the ecommerce info!
That always was my pet peeve too. All that info about databases and at the
end of the book.....you're not even close to actual money transfers.
Rick Strahl does a fantastic job of covering this topic with all you need to
know without the hernia of yet another fluffy desk reference.
While I'm on a semi-rant..... There was a book (I still have it) "1001
Visual Basic Programmer's Tips" by JAMSA Press. It is one of the most
succinct books on Visual Basic 6 programming ever written. It doesn't build
an entire confusing, convoluted application to teach you about programming.
It shows you 1001 How-To's in a basic, straightforward manner. Each lesson
is usually less than a page.
Those whole-app-books require you to read it beginning to end to make sure
you didn't miss anything in the app that may mess up what you are trying to
do (public variables, enums and class libraries covered in other chapters).
What a waste of time....especially in a book about a RAD development tool
like VB.
A complete VB beginner that can write an idea for an app in pseudo code can
take the pseudo code and "1001 Visual Basic Programmer's Tips" and be
productive immediately. (Perfect? No. Productive? Yes!)
It is simply beautiful. The closest thing to it dealing with .Net is the
"C/C++/C# Programmer's Bible" also by JAMSA Press. It has the same style
but covers 3 languages lightly instead of any single language in depth. Oh,
it teaches you what you need to know....just not what you want to know.
I contacted the author of "1001 Visual Basic Programmer's Tips" and begged
him to do one on VB.Net. Alas, he has no plans to do so at this time and is
no longer with JAMSA Press.
RAD tools need RAD lessons. Most VB programmer's don't want to be MIS
Professors....and those that do don't mind the long-winded books that are
out currently.
There are a few good books that get close to the 1001 style. Microsoft puts
out a decent version in the "Microsoft Visual Basic.Net Programmer's
Cookbook" and there's the Wrox book "Visual Basic.Net Solutions Toolkit".
Both show simple solutions to "How do I..." questions.
Hey...that gives me an idea......and it isn't writing yet another long
winded programmers book.
Thanks again for the link to your blog.
Awesome link to the ecommerce info!
That always was my pet peeve too. All that info about databases and at the
end of the book.....you're not even close to actual money transfers.
Rick Strahl does a fantastic job of covering this topic with all you need to
know without the hernia of yet another fluffy desk reference.
While I'm on a semi-rant..... There was a book (I still have it) "1001
Visual Basic Programmer's Tips" by JAMSA Press. It is one of the most
succinct books on Visual Basic 6 programming ever written. It doesn't build
an entire confusing, convoluted application to teach you about programming.
It shows you 1001 How-To's in a basic, straightforward manner. Each lesson
is usually less than a page.
Those whole-app-books require you to read it beginning to end to make sure
you didn't miss anything in the app that may mess up what you are trying to
do (public variables, enums and class libraries covered in other chapters).
What a waste of time....especially in a book about a RAD development tool
like VB.
A complete VB beginner that can write an idea for an app in pseudo code can
take the pseudo code and "1001 Visual Basic Programmer's Tips" and be
productive immediately. (Perfect? No. Productive? Yes!)
It is simply beautiful. The closest thing to it dealing with .Net is the
"C/C++/C# Programmer's Bible" also by JAMSA Press. It has the same style
but covers 3 languages lightly instead of any single language in depth. Oh,
it teaches you what you need to know....just not what you want to know.
I contacted the author of "1001 Visual Basic Programmer's Tips" and begged
him to do one on VB.Net. Alas, he has no plans to do so at this time and is
no longer with JAMSA Press.
RAD tools need RAD lessons. Most VB programmer's don't want to be MIS
Professors....and those that do don't mind the long-winded books that are
out currently.
There are a few good books that get close to the 1001 style. Microsoft puts
out a decent version in the "Microsoft Visual Basic.Net Programmer's
Cookbook" and there's the Wrox book "Visual Basic.Net Solutions Toolkit".
Both show simple solutions to "How do I..." questions.
Hey...that gives me an idea......and it isn't writing yet another long
winded programmers book.
Thanks again for the link to your blog.
Ken Cox said:You'd probably want a setup routine to make the changes using caspol.
Anyway, I'm with you that VSTO has problem when it comes to real-world
usage:
http://weblogs.asp.net/kencox/archi...tment-with-VSTO-2005-Internet-Deployment.aspx
Ken
Microsoft MVP [ASP.NET]
ljh said:This may be moot at this point......
After I read the "Granting and Removing Permissions for an Office
Solution" thing, there's simply no way an end user would EVER do this to
grant permissions for an Office solution.
I hope like hell that I misunderstood something. Do they really expect
end users to ...
1.. Open Microsoft .NET Framework 2.0 Configuration again.
2.. Right-click the VSTOProjects node, and then click New on the
shortcut menu.
3.. Enter the name Security Test Strong Name for the new code group, and
then click Next.
4.. In the Choose the condition type for this code group list, click
Strong Name.
5.. Click Import.
6.. Browse to C:\Walkthroughs\My Security Test\My Security Test\bin\My
Security Test.dll for Visual Basic or C:\Walkthroughs\My Security Test\My
Security Test\bin\debug\My Security Test.dll for C#, and then click Open.
7.. Click Next.
8.. Click Next to accept the FullTrust permission set, and then click
Finish.
9.. Close Microsoft .NET Framework 2.0 Configuration.
My users are damned lucky to understand how a mouse works. They'll
never get this.
If I haven't misunderstood something, this really sucks for developing
Office solutions in .Net. It just won't happen.
M
Mr Flibble
* ljh said:Thanks for the link!
It really does sucj because I LOVE Office. Open Office doesn't begin to
offer the slick UI and feature set that MS Office does.
Office is over ten years old. Give OO time.
L
ljh
The problem with OO (as with Linux in general) is that it is constantly
trying to copy MS Office.
As long as they do they will always be a step behind. It is inevitable. If
you are always trying to be compatible with or emulate functions of MSO,
you are playing catch up.
OO and Linux need to stand on thier own webbed feet and nove forward with
thier own great ideas (like open document standards). Only then will OO and
Linux be real competitors for the desktop.
trying to copy MS Office.
As long as they do they will always be a step behind. It is inevitable. If
you are always trying to be compatible with or emulate functions of MSO,
you are playing catch up.
OO and Linux need to stand on thier own webbed feet and nove forward with
thier own great ideas (like open document standards). Only then will OO and
Linux be real competitors for the desktop.