Re: Web Service Stack trace .. - C# Discussion Boards

mamoony10-Sep-12 11:45

10-Sep-12 11:45

Hi

I want to use windows login box in my c# application which is secure and pass values using tokens. I do not want to create a custom login box. How to popup the login screen?

Thanks in advance,
Sai

Re: Windows Login Box

Michael_Lu10-Sep-12 12:18

Michael_Lu

10-Sep-12 12:18

Hi,
I am assuming the C# application you mentioned is a Windows Form application. In that case, I think the LogonUser API is what you are looking for. You can see this article for more info (http://stackoverflow.com/questions/2905407/how-to-use-windows-authentication-in-windows-application)[^]

Re: Windows Login Box

mamoony11-Sep-12 3:39

mamoony

11-Sep-12 3:39

Thank you very much Smile | :)

...

Re: Windows Login Box

Abhinav S10-Sep-12 18:35

Abhinav S

10-Sep-12 18:35

You can use a simple Windows Forms Login Control component[^] that has already been built. All you need to do is include this in your program.

Windows Phone Apps - XKCD | Calvin | SMBC | Dilbert | Speed Dial

Re: Windows Login Box

mamoony11-Sep-12 3:43

mamoony

11-Sep-12 3:43

Is this a custom built? I do not want to use custom built. I did one myself using Active directory directory service reference and the company do not want it.

Thank you,
Sai

Web Service Stack trace ..

UBX10-Sep-12 5:02

UBX

10-Sep-12 5:02

I have a web service stack trace where the method is called GetLoadTrace();
However, I can't seem to find what line the error occured in . Does the stack trace tell you ?

It just says GetLoadTrace()+90
GetLoadTrace()+155

What line did the error occur on then ? Does it NOT tell you ?

==================================================

--I am the STIG !!!!!!!!!!!!!!!!!

Re: Web Service Stack trace ..

Dave Kreskowiak10-Sep-12 6:57

Dave Kreskowiak

10-Sep-12 6:57

The exception is usually thrown in the method at the very top of the stack trace.

The stack trace does NOT tell you on which line the problem occured in a Release compiled application, only the method in which it occured.

A guide to posting questions on CodeProject[^]

Dave Kreskowiak

Re: Web Service Stack trace ..

BobJanova11-Sep-12 1:23

BobJanova

11-Sep-12 1:23

It's not actually release/debug, it's whether a .pdb file is present ... but I don't think it's possible to make a .pdb for a release build so you can never get line numbers in a release stack trace.

Re: Web Service Stack trace ..

Pete O'Hanlon11-Sep-12 1:36

Pete O'Hanlon

11-Sep-12 1:36

BobJanova wrote:
I don't think it's possible to make a .pdb

You can. A release build is not magic, the main difference is just that the debug version doesn't optimise the code. If you do a release build, take a look in your Release folder - you'll see a number of generated PDB files in there.

To prevent generation of release PDV files, select Project Properties > Build > Advanced > Debug Info: None (make sure the configration is set to Release when you do this).

*pre-emptive celebratory nipple tassle jiggle* - Sean Ewington

"Mind bleach! Send me mind bleach!" - Nagy Vilmos

CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier

Re: Web Service Stack trace ..

BobJanova11-Sep-12 1:44

BobJanova

11-Sep-12 1:44

Oh, I thought that the optimisations made it too hard for the compiler to know what to create.

If I'm using csc, and I use /debug to create a .pdb, then, is that still 'release' code (i.e. optimised etc)?

Re: Web Service Stack trace ..

Pete O'Hanlon11-Sep-12 2:56

Pete O'Hanlon

11-Sep-12 2:56

It's not release code if you use csc /debug. If you want to do the release build that you get with Visual Studio, just use csc.exe /optimize+ /debug:pdbonly. To just produce the release build without the pdb, just use csc.exe /optimize+.

*pre-emptive celebratory nipple tassle jiggle* - Sean Ewington

"Mind bleach! Send me mind bleach!" - Nagy Vilmos

CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier

Re: Web Service Stack trace ..

Dave Kreskowiak11-Sep-12 3:03

Dave Kreskowiak

11-Sep-12 3:03

The compiler will know what to create easy enough.

My problem is with optimizations and code rewrite, are the line numbers going to be accurate??

A guide to posting questions on CodeProject[^]

Dave Kreskowiak

Help File Authoring

Bart10-Sep-12 4:07

Bart

10-Sep-12 4:07

I need to create a help file for an application. Not code comments but actual "how to use" help file for end users.

Which "tool" should I use?
Which tool have you used? Did you think it was good? Why?
Which tool shouldnt I use? Why not?

Thanks

bart

Re: Help File Authoring

Pete O'Hanlon10-Sep-12 4:13

Pete O'Hanlon

10-Sep-12 4:13

This isn't really an appropriate question for the C# forum. What you could do is download and test some of the help authoring tools to see which best suits your requirements.

*pre-emptive celebratory nipple tassle jiggle* - Sean Ewington

"Mind bleach! Send me mind bleach!" - Nagy Vilmos

CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier

Re: Help File Authoring

Bart10-Sep-12 4:42

Bart

10-Sep-12 4:42

Can you suggest a better forum?

bart

Re: Help File Authoring

Pete O'Hanlon10-Sep-12 4:47

Pete O'Hanlon

10-Sep-12 4:47

Possibly the lounge. And rather than post your question like this, I'd rephrase it to be a more general "does anyone have any experience with help authoring tools? I'm interested in which tools people have used to write documentation for end users, rather than API style documentation, and how they found them."

*pre-emptive celebratory nipple tassle jiggle* - Sean Ewington

"Mind bleach! Send me mind bleach!" - Nagy Vilmos

CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier

Re: Help File Authoring

Bart10-Sep-12 4:57

Bart

10-Sep-12 4:57

so you will answer in the lounge? Without any elephants?

bart

Re: Help File Authoring

Pete O'Hanlon10-Sep-12 5:05

Pete O'Hanlon

10-Sep-12 5:05

Some might - when you post, put in that I suggested that you posted there.

*pre-emptive celebratory nipple tassle jiggle* - Sean Ewington

"Mind bleach! Send me mind bleach!" - Nagy Vilmos

CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier

Re: Help File Authoring

Bernhard Hiller10-Sep-12 23:07

Bernhard Hiller

10-Sep-12 23:07

Good point.
We "use" Microsoft HTML Help Workshop 1.3 - it's old, and it's not good to use. (And we hardly ever use it, our help files are really outdated).
At a different company, the documentation guys used RoboHelp. It allowed for better help integration than the HTML Workshop, you could generate context-sensitive help downto the controls on a form. But I do not know how hard it is to use.

Re: Help File Authoring

BobJanova11-Sep-12 1:26

BobJanova

11-Sep-12 1:26

These days I just create HTML pages and have the F1 link point a browser at it. The classic .hlp type help is no longer supported under recent Windows, and .chm help is just HTML but annoying to use.

System.AccessViolationException openfiledialog win7

Rahul Sabharwal10-Sep-12 2:29

Rahul Sabharwal

10-Sep-12 2:29

My project was created in winxp and now migrated to windows7. I am getting a weird exception while click on the openfiledialog icon in my project and the application crashes after this. This only happens when I create a release build and install that build in windows 7.

The setup is also created in the windows 7. I do no get this exception when run the code in the debug mode.

I am setting the initialdirectory property of the openfiledialog to desktopdirectory.

Below is the exception trace i caught in the windows event viewer.

Application: projectname.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.

Exception Info: System.AccessViolationException

Stack:

at System.Windows.Forms.UnsafeNativeMethods.GetOpenFileName(OPENFILENAME_I)

at System.Windows.Forms.OpenFileDialog.RunFileDialog(OPENFILENAME_I)

at System.Windows.Forms.FileDialog.RunDialogOld(IntPtr)

at System.Windows.Forms.FileDialog.RunDialog(IntPtr)

at System.Windows.Forms.CommonDialog.ShowDialog(System.Windows.Forms.IWin32Window)

at System.Windows.Forms.CommonDialog.ShowDialog()

at companyname.projectname.MainForm.processFileOperation(FileOperationType)

at companyname.projectname.MainForm.fileOpenMenuItem_Click(System.Object, System.EventArgs)

at companyname.projectname.MainForm.toolBar_ButtonClick(System.Object, System.Windows.Forms.ToolBarButtonClickEventArgs)

at System.Windows.Forms.ToolBar.OnButtonClick(System.Windows.Forms.ToolBarButtonClickEventArgs)

at System.Windows.Forms.ToolBar.WmReflectCommand(System.Windows.Forms.Message ByRef)

at System.Windows.Forms.ToolBar.WndProc(System.Windows.Forms.Message ByRef)

at System.Windows.Forms.Control+ControlNativeWindow.OnMessage(System.Windows.Forms.Message ByRef)

at System.Windows.Forms.Control+ControlNativeWindow.WndProc(System.Windows.Forms.Message ByRef)

at System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr)

at System.Windows.Forms.UnsafeNativeMethods.SendMessage(System.Runtime.InteropServices.HandleRef, Int32, IntPtr, IntPtr)

at System.Windows.Forms.Control.SendMessage(Int32, IntPtr, IntPtr)

at System.Windows.Forms.Control.ReflectMessageInternal(IntPtr, System.Windows.Forms.Message ByRef)

at System.Windows.Forms.Control.WmCommand(System.Windows.Forms.Message ByRef)

at System.Windows.Forms.Control.WndProc(System.Windows.Forms.Message ByRef)

at System.Windows.Forms.ScrollableControl.WndProc(System.Windows.Forms.Message ByRef)

at System.Windows.Forms.Form.WndProc(System.Windows.Forms.Message ByRef)

at System.Windows.Forms.Control+ControlNativeWindow.OnMessage(System.Windows.Forms.Message ByRef)

at System.Windows.Forms.Control+ControlNativeWindow.WndProc(System.Windows.Forms.Message ByRef)

at System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr)

at System.Windows.Forms.UnsafeNativeMethods.CallWindowProc(IntPtr, IntPtr, Int32, IntPtr, IntPtr)

at System.Windows.Forms.NativeWindow.DefWndProc(System.Windows.Forms.Message ByRef)

at System.Windows.Forms.Control.DefWndProc(System.Windows.Forms.Message ByRef)

at System.Windows.Forms.Control.WmMouseUp(System.Windows.Forms.Message ByRef, System.Windows.Forms.MouseButtons, Int32)
at System.Windows.Forms.Control.WndProc

(System.Windows.Forms.Message ByRef)

at System.Windows.Forms.ToolBar.WndProc(System.Windows.Forms.Message ByRef)

at System.Windows.Forms.Control+ControlNativeWindow.OnMessage(System.Windows.Forms.Message ByRef)

at System.Windows.Forms.Control+ControlNativeWindow.WndProc(System.Windows.Forms.Message ByRef)

at System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr)

at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG ByRef)

at System.Windows.Forms.Application
+ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr, Int32, Int32)

at System.Windows.Forms.Application+ThreadContext.RunMessageLoopInner(Int32, System.Windows.Forms.ApplicationContext)

at System.Windows.Forms.Application+ThreadContext.RunMessageLoop(Int32, System.Windows.Forms.ApplicationContext)

at System.Windows.Forms.Application.Run(System.Windows.Forms.Form)

at companyname.projectname.MainForm.Main(System.String[])

Re: System.AccessViolationException openfiledialog win7

Eddy Vluggen10-Sep-12 2:40

Eddy Vluggen

10-Sep-12 2:40

This is not caused by a building a release-mode or creatng a setup on Windows 7. First, you'll need to implement an event[^] to deal with "unhandled exceptions". Next, you'd need to debug to find out the cause of the exception; my guess is that the filename or the path is mukking up things.

Can you post the code that calls your dialog? And the filename/path that you select? And the initial directory you try to set?

Bastard Programmer from Hell Suspicious | :suss:

if you can't read my code, try converting it here[^]

Re: System.AccessViolationException openfiledialog win7

Rahul Sabharwal10-Sep-12 2:47

Rahul Sabharwal

10-Sep-12 2:47

<pre lang="c#">OpenFileDialog dlg = new OpenFileDialog();
                        
                        #endregion

                        #region DIALOG BOX SETTINGS
                        string previousOpenFilePath = Environment.GetFolderPath(Environment.SpecialFolder.DesktopDirectory);
                        
                        dlg.RestoreDirectory = true;
                        dlg.DefaultExt = ".xml";
                        dlg.Filter = "XML Document (*.xml)|*.xml|Excel File (*.xls)|*.xls|Excel File (*.xlsx)|*.xlsx|VPI File (*.vpi)|*.vpi|All Files (*.*)|*.*";
                        #endregion

                        dlg.CheckPathExists = true;
                        dlg.CheckFileExists = true;
                        if (dlg.ShowDialog() == DialogResult.OK)

Here the exception comes at the showdialog call. The stacktrace goes in eventviewer.

Re: System.AccessViolationException openfiledialog win7

Eddy Vluggen10-Sep-12 3:31

Eddy Vluggen

10-Sep-12 3:31

Looks good Smile | :)

..and how does the filename/initial path look like?

Bastard Programmer from Hell Suspicious | :suss:

if you can't read my code, try converting it here[^]

NamedPipeServerStream.GetAccessControl

True_Posi10-Sep-12 1:10

True_Posi

10-Sep-12 1:10

Hello!

I created a process containing a NamedPipeServerStream and second process NamedPipeClientStream.

I managed to establish communication between both processes on the same server. Is also worked on two different computers over the network, after I created the same USER and Password on both computers.

But it only worked, if after i assigend the group "Administartors" to the users. Is it possible to establish connection between without beeing Administrator?

My first Try:

NamedPipeServerStream m_PipeServerStream = new NamedPipeServerStream(
    Properties.Settings.Default.PIPE_NAME
    , PipeDirection.InOut
    , SERVER_THREADS
    , PipeTransmissionMode.Byte
    , PipeOptions.Asynchronous
    , BUFFER_SIZE_kB
    , BUFFER_SIZE_kB);

if (Properties.Settings.Default.SERVER_USER.Count > 0)
{
    foreach (string item in Properties.Settings.Default.SERVER_USER)
    {
        m_PipeServerStream.GetAccessControl().AddAccessRule(new PipeAccessRule(
            item
            , PipeAccessRights.ReadWrite
            , System.Security.AccessControl.AccessControlType.Allow));
    }
}

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.