Save As dialog in C#

In VBA I was using the following code to open the iMan Save As dialog:

Dim objCmd As CommandBarButton
Set objCmd = Word.CommandBars("File").FindControl(ID:=748) ' File|Save As
objCmd.Execute

But now I'm using a seperate c# addin instead of a template. Is there a way to call the iMan Save As dialog via c#?

Thanks

Find more posts tagged with

Comments

jny

It should still work just the same except that your code would be in C#.

po8crg

I'm using a VB.NET add-in, but I'm having exactly the same problem as you are with the same code:

'appWord is the current instance of Word, passed as a parameter

Dim objMenuBar As CommandBar
Dim objSaveButton As CommandBarButton
objMenuBar = appWord.CommandBars("File")
objSaveButton = objMenuBar.FindControl(Id:=748)
objSaveButton.Execute()

The problem is that I get the local save window, not the integrated one.

I suspect that it's something to do with the way Word deals with multiple add-ins, ie the iManOXP.dll add-in and our integrated add-in. I think Word is returning the native save button, even though we are trying to use the integrated one.

I tried calling a VBA macro from the add-in, and the behaviour is really strange: if the macro is called from the add-in, then I get a Word save as window (local save as); if the macro is run directly, then I get the integrated save as window.

Can anyone help?

po8crg

OK, this is definitely very strange.

I directly called the "FileSaveAsBinding" macro, which is in the iManO2K.dot template, supplied by Interwoven as part of the normal Office integration.

That did a normal save, not an integrated save. Call the same macro directly, rather than from the add-in, and it works fine (but I can't do that).

So I tried putting in a breakpoint, and having a look at Word. With a thread in the add-in, even actually hitting the save button gets a non-integrated save.

Obviously, if I'm calling code from an add-in, the WorkSite integration - ie iManOXP.dll - is disabled, while the add-in is running, so I can't call from one add-in to another via Word.

There doesn't seem to be a public entry point in iManOXP.dll to call the save as routine.

Am I going to have to completely reimplement the "save as" function in order to deliver this functionality?

po8crg

Am I going to have to completely reimplement the "save as" function in order to deliver this functionality?

A: Yes, but it's not that hard. This is a VB.NET version:

Save the document using the normal Word save routines, put the path/filename in strFileName and close it.
Add this to the declarations:
Private Declare Function FindWindow Lib "user32" Alias "FindWindowA" (ByVal lpClassName As String, ByVal lpWindowName As String) As Integer

And this does the saving:

Dim dmsConnection As IManage.IManDMS = New IManage.ManDMSClass()
dmsConnection.ApplicationName = "My Application"
Dim mySession As IManage.IManSession = dmsConnection.Sessions.Add("DMS Server / Cluster Name")
mySession.TrustedLogin()
Dim hwndWord As Integer
hwndWord = FindWindow("OpusApp", Word.Caption)
Dim intKeepCheckedOut As Integer
Dim docJustSaved As IManage.NRTDocument
Dim objImportCmd As IMANEXTLib.ImportCmd
Dim objContextItems As New IMANEXTLib.ContextItems
objContextItems.Add("ParentWindow", hwndWord)
objContextItems.Add("DestinationObject", sesCobbDms)
objContextItems.Add("IManExt.Import.FileName", strFileName)
intKeepCheckedOut = IManage.CheckinOptions.nrDontKeepCheckedOut
objContextItems.Add("IManExt.Import.KeepCheckedOut", intKeepCheckedOut)
objImportCmd = New IMANEXTLib.ImportCmd
objImportCmd.Initialize(objContextItems)
objImportCmd.Update()
objImportCmd.Execute()
If objContextItems.Item("IManExt.Refresh") Then
docJustSaved = objContextItems.Item("ImportedDocument")
docJustSaved.CheckOut(strCorrectCheckOutLocationInNrPortbl, IManage.CheckOutOptions.nrReplaceExistingFile, Now(), "Just Created")
Word.Documents.Open(docJustSaved.CheckoutPath)
Else
Word.Documents.Open(strFileName)
End If

There is quite a bit of tidying up to do on this, but it should be an adequate basic version. Obviously, you'll have to translate from VB.NET to C# and put in some proper error handling (I took it all out for clarity)

RJKnott

C# version (written for an explorer "send to" application)
(iDMS is a MANDMS with a connected session)

string path ="c:doc.doc"

FileInfo fFile = new FileInfo(Path);
IMANEXT2Lib.IManFileSaveCmd iDlg = new IMANEXT2Lib.IManFileSaveCmd();
IMANEXTLib.ContextItems iCt = new IMANEXTLib.ContextItems();
iCt.Add("ImanDMS", iDMS);
iCt.Add("DocOpenLocation", Path);
if (fFile.Extension.ToLower() == ".url")
{
iCt.Add("IManExt.Import.DocType", "URL");
}
else
{
try
{
string type = iSession.Databases.ItemByIndex(1).GetDocumentTypeFromPath(Path).Name;
iCt.Add("IManExt.Import.DocType", type);
}
catch
{
}
}
iCt.Add("IManExt.Import.DocDescription", fFile.Name.Substring(0, fFile.Name.Length - fFile.Extension.Length));
iDlg.Initialize(iCt);
iDlg.Update();
iDlg.Execute();

Andrew_Sellors

If you have a COM add-in and are trying to call the open or save menu items to get the Office integration, it doesn't work properly if called directly from the COM add-in (you get the standard office dialog instead). I think the problem may be to do with the context of where you are making the call, if you call it from a response to a menu click event in the COM Add-in for example, it doesn't work but it does if you call it from outside this context, it does.

The work round which I have used for a while it to utilise a Timer event to actually Execute the menu item. Rather than Execute the menu item directly in your code, enable a Timer which has no delay. When the Timer fires, it disables itself so you only get one shot and Executes the menu item you want. This makes the Execute run in another thread and it works. I have used this in VB6 and .NET (1.1 and 2.0).

Andrew